{
  "schema": "varexis-public-evidence-record/0.3",
  "generated_at_utc": "2026-10-18T13:45:35.999Z",
  "record_id": "VXI-EXT-PROCUREMENT-COINBASE-SPEND-PERMISSION-01-v1",
  "record_kind": "external_reference",
  "title": "Coinbase: Recurring token allowance has a defined scope",
  "system": "Coinbase Spend Permissions",
  "evidence_family": "vendor_evidence_review",
  "index_status": "PUBLIC_SAFE_SOURCE_REVIEW",
  "evidence_state": "PRIMARY_DOCUMENTATION_REVIEW_ONLY",
  "canonical_question": "Does a Coinbase spend permission give an agent arbitrary control of the wallet?",
  "near_questions": [
    "Can the spender make any contract call from this wallet?",
    "Is this token allowance recurring or for one purchase?",
    "Which spender address received the delegated permission?",
    "Does the approved allowance cover this token transfer?",
    "Can a wallet permission stand in for procurement approval?",
    "What restricts the scope of Coinbase Spend Permissions?",
    "What evidence shows the permission was revoked onchain?",
    "Does signing a spend permission prove revocation is complete?",
    "Can an agent reuse a recurring allowance for another purchase?",
    "Which token and period belong in the spending review?",
    "Does the transfer mechanism validate our internal buying policy?",
    "What separates wallet transfer authority from order approval?"
  ],
  "supported_claims": [
    {
      "claim": "Coinbase documents Spend Permissions as recurring native-token or ERC-20 spending delegated to a spender address. The manager checks spending against the approved allowance; the design does not authorise arbitrary external calls from the user account. Permission revocation is a separate onchain operation. A recurring allowance is not evidence of a one-time procurement approval.",
      "reliance": "DOCUMENTED_CAPABILITY_ONLY"
    }
  ],
  "not_demonstrated_claims": [
    "Verified buyer configuration, actual data erasure, effective access or completed business actions",
    "Legal advice, compliance determination, vendor certification or safety assurance",
    "Runtime enforcement, permission to act or expanded licensed-checker coverage"
  ],
  "public_summary": "Coinbase documents Spend Permissions as recurring native-token or ERC-20 spending delegated to a spender address. The manager checks spending against the approved allowance; the design does not authorise arbitrary external calls from the user account. Permission revocation is a separate onchain operation. A recurring allowance is not evidence of a one-time procurement approval.",
  "related_record_ids": [],
  "source_review": {
    "source_type": "official_external_documentation",
    "source_title": "Coinbase: Spend Permissions",
    "source_url": "https://github.com/coinbase/spend-permissions",
    "checked_on": "2026-10-18",
    "candidate_record_id": "VXI-EXT-PROCUREMENT-COINBASE-SPEND-PERMISSION-01-v1",
    "candidate_record_sha256": "d12249c7b1475e47329bb81c607641ea0722c49fc5a6a3657a700dc0e9d408ee",
    "method": "Primary documentation reviewed for the published bounded statement.",
    "deployment_tested_by_varexis": false,
    "revalidation": "The delivered snapshot preserves the review date shown. Recheck current primary documentation and deployment context before relying on present applicability; payment does not trigger fresh research."
  },
  "answer_policy": {
    "classification": "DOCUMENTED_WITH_DEPLOYMENT_BOUNDARY",
    "bounded_answer": "Coinbase documents Spend Permissions as recurring native-token or ERC-20 spending delegated to a spender address. The manager checks spending against the approved allowance; the design does not authorise arbitrary external calls from the user account. Permission revocation is a separate onchain operation. A recurring allowance is not evidence of a one-time procurement approval.",
    "required_buyer_context": "The account, spender, token, period and approved allowance. The intended purchase and the authority granted outside the transfer mechanism. The applicable permission approval, spend and revocation state. Buyer deployment not inspected.",
    "missing_evidence": "A broader claim needs evidence matching the intended use. Payment does not upgrade the evidence state."
  },
  "private_boundary": "Raw logs, thresholds, private paths, source code, protected mechanisms and reconstruction-level details are excluded from public and paid delivery.",
  "decision_profile": {
    "schema": "varexis-vendor-evidence-review/1",
    "review_status": "documentation_review_only",
    "checked_on": "2026-10-18",
    "claim_to_check": "Does a Coinbase spend permission give an agent arbitrary control of the wallet?",
    "documented_statement": {
      "status": "documented",
      "statement": "Coinbase documents Spend Permissions as recurring native-token or ERC-20 spending delegated to a spender address. The manager checks spending against the approved allowance; the design does not authorise arbitrary external calls from the user account. Permission revocation is a separate onchain operation. A recurring allowance is not evidence of a one-time procurement approval.",
      "source_ids": [
        "coinbase-spend"
      ]
    },
    "buyer_evidence_required": [
      "The account, spender, token, period and approved allowance.",
      "The intended purchase and the authority granted outside the transfer mechanism.",
      "The applicable permission approval, spend and revocation state."
    ],
    "review_condition": {
      "status": "varexis_review_policy",
      "statement": "Do not infer one-time purchase approval, arbitrary call authority or completed revocation from the presence of a spend-permission signature."
    },
    "unknowns": "The buyer configuration, contract, effective entitlement and operational evidence have not been inspected. Missing evidence does not establish absence or failure of the feature.",
    "evidence_sources": [
      {
        "source_id": "coinbase-spend",
        "url": "https://github.com/coinbase/spend-permissions",
        "final_url": "https://github.com/coinbase/spend-permissions",
        "title": "Coinbase: Spend Permissions",
        "checked_on": "2026-10-18",
        "captured_at_utc": "2026-10-18T13:33:51.368Z",
        "version_context": "Official repository README captured on the review date; native and ERC-20 token delegation",
        "sha256": "030c406722fde409ee4fb9e722241277a0127c460c4ec4db7e5ce67aab5db1e6",
        "bytes": 340940,
        "hash_basis": "Decoded HTTP response body bytes; identifies captured content, not truth or certification",
        "reviewed_sections": [
          "Does a Coinbase spend permission give an agent arbitrary control of the wallet?"
        ]
      }
    ],
    "observed_deployment": false,
    "commercial_reliance_boundary": "Procurement evidence support only; no supplier clearance, legal conclusion, configuration audit or verification of the buyer's claim is supplied.",
    "paid_value": {
      "decision_context": "A wallet operator must distinguish a recurring transfer allowance from a particular purchase approval or unrestricted account authority.",
      "free": "Complete review, practical questions, sources and limitations; may be saved locally.",
      "single_request": "Existing server-saved version-bound route snapshot for later authenticated retrieval.",
      "evidence_receipt": "The same snapshot plus the existing unsigned delivery receipt.",
      "excluded": [
        "Fresh vendor research",
        "Continuous monitoring or change alerts",
        "Testing the buyer configuration",
        "Private evidence or vendor certification"
      ],
      "integrity": "Hashes identify content versions; they do not prove truth or provide a signature."
    },
    "revalidation": {
      "trigger": "A saved purchase does not recheck the source or buyer configuration.",
      "specific_watch": "The account, spender, token, period and approved allowance. The intended purchase and the authority granted outside the transfer mechanism. The applicable permission approval, spend and revocation state."
    },
    "buyer_relevance": "A wallet operator must distinguish a recurring transfer allowance from a particular purchase approval or unrestricted account authority.",
    "refusal_conditions": [
      "Do not infer one-time purchase approval, arbitrary call authority or completed revocation from the presence of a spend-permission signature."
    ]
  },
  "niche": {
    "label": "Agent Authority & Action Evidence",
    "niche_id": "agent-authority-action-evidence",
    "topic_id": "delegated-spending",
    "buyer_intent": "A wallet operator must distinguish a recurring transfer allowance from a particular purchase approval or unrestricted account authority."
  },
  "paid_access_note": "The full published answer and boundaries are free. Paid access saves the selected route and source versions, with an unsigned receipt when purchased. Preview coverage before paying. Fresh research, bespoke assessment and protected evidence are excluded.",
  "service_route": {
    "request_guide": "/varexis-index/request.html",
    "request_workflow": "/varexis-index/request-workflow.json",
    "service_id": "single_request",
    "service_routes_url": "/varexis-index/service-routes.json",
    "payment_required": true,
    "availability_endpoint": "/api/index/capabilities",
    "operational_status": "AUTOMATIC_SERVICE_CAPABILITIES_GATED",
    "checkout_url": "/index-access"
  },
  "authority_boundary": "VAREXIS-INDEX informs evidence reliance. It does not provide advice, certification, deployment authority, security assurance, production approval, or guarantee.",
  "human_page": "/varexis-index/catalog.html#coinbase-recurring-token-spend-authority",
  "machine_readable_record": "/varexis-index/records/coinbase-recurring-token-spend-authority.json"
}
