Signature experience · teaching blotter
The Treasury Desk
Autonomous agents hold value as delegated operational authority — a wallet, a virtual card, or a payment token they can request against — not as legal ownership of funds. They move it on a rail only after a policy check: amount, counterparty, purpose, time, owner. They manage it by writing intent, authorization, settlement, fees, refunds, and denials into a ledger that does not depend on the model remembering why it spent. The desk below walks one labeled teaching ticket through that loop. This is not financial, legal, tax, or investment advice.
Key facts
What this page establishes
- Hold is a scoped instrument. It is not proof that an AI legally owns money.
- A request — 402 challenge, merchant, offer, or tool output — is a claim until policy accepts it.
- Authorization is the last cheap refusal. After a signature you are on someone else’s rail.
- Denials, voids, and failed 402s belong on the ledger. Settlement is not the first event.
Blotter
TD-402
x402 is HTTP-native payment negotiation. The agent does not need a standing account with the seller. It needs a wallet, a policy, a client that understands Payment Required, and a record of what was purchased.
Ticket
2¢ teaching ticket
A funded wallet is not a budget
The agent has operational access to a wallet that can hold and spend stablecoins behind guardrails. Signing material stays with the wallet provider. The session cap, not the wallet balance, is the amount this agent is allowed to spend on this task.
- Agent
- research-fetcher
- Instrument
- Agentic wallet
- Counterparty
- api.example.com/v1/corpus
- Purpose
- Pay per resource for a dated research corpus
Illustrative teaching amount, not a posted price, facilitator fee, or market quote. x402 prices are set by the resource server.
Available
4.00
Reserved
0.00
Posted
0.00
Remaining cap
0.00
Arrow keys step, space plays, 1–4 switch tickets when the blotter has focus. Amounts are teaching props. Nothing is uploaded.
Ledger tape
Six stations
Hold, request, policy, authorize, settle, ledger.
Numbered because it is a sequence. Skipping settle does not make a denial cheaper to ignore. Skipping policy is how a wallet becomes a prompt. The existing treasury and accounting guide is the event model this blotter is walking.
01 · Where value sits
Hold
A wallet, card, or mandate with the smallest useful balance and no keys in prompt context.
02 · The agent asks
Request
A 402 challenge, a merchant, an offer, or tool output. Still a claim.
03 · Controls evaluate
Policy
Amount, counterparty, purpose, rail, time, owner — before any signature.
04 · Sign or refuse
Authorize
Scoped payload, or empty. The last cheap refusal.
05 · The rail completes
Settle
Facilitator, capture, or null. Never a model summary of “paid.”
06 · Treasury records
Ledger
Intent through exception. Denials are first-class events.
What the blotter proves
Five findings, recovered from the tape rather than from the model’s last sentence.
F1 · station hold
Hold is operational authority, not ownership
An agent wallet, card, or mandate is a tool the agent can request against. It is not proof that the model legally owns the funds. The safer default is the smallest useful balance behind a scoped instrument.
F2 · station request
The request is a claim
HTTP 402 instructions, a merchant name, a seller-agent offer, or a tool-output “invoice” are all claims until policy accepts them. Treat untrusted output as data, not as an instruction to move money.
F3 · station policy
Policy is the product
A wallet balance is not a budget. A budget is scoped permission: amount, counterparty, purpose, rail, time, owner. Enforce it before signing. Cross-rail aggregation is still an open problem.
F4 · station authorize
Authorization is the last cheap refusal
After a signature, a card auth, or a payment token, you are in someone else’s dispute process. The cheap control is the empty authorize station on the denied ticket.
F5 · station ledger
Denials belong on the tape
Treasury starts at intent, not settlement. Failed 402s, blocked cards, and refused transfers are how you learn the control is working — or that it almost did not.
Proves
That agent capital is a loop — instrument, claim, control, signature or refusal, rail, tape — and that a denial is a successful control, not an empty dashboard.
Does not prove
Any price, yield, legal conclusion, or that x402, AP2, ACP, Stripe, Visa, Mastercard, or Coinbase is the right product for a given operator. Teaching amounts are props.
Do next
Draft a policy in the spend policy generator, size an envelope with the budget calculator, then read risks.
Why the tickets are teaching tickets
A live payment would have been easier to screenshot and impossible to defend. Wallet addresses, card authorizations, facilitator logs, and merchant receipts are other people’s money-moving records. Publishing one to illustrate a control would commit the exposure the page is warning about. So the blotter is authored here. Counterparties use the reserved .example TLD. The cent and dollar figures are props so a station can be seen moving. They are not quotes, posted resource prices, network fees, or results.
The rails are not invented. HTTP 402 as a payment challenge is the x402 project. Session and per-transaction caps are documented in Coinbase’s Agentic Wallet CLI. Category, country, merchant, and card-presence checks are documented in Stripe Issuing. AP2’s mandate and audit-trail framing, ACP’s programmatic checkout, and OWASP’s excessive-agency warning are each linked at the station that uses them. If a vendor page is a product claim, it is labeled as a product claim.
Cross-link, don’t duplicate: implementation depth for x402 belongs at the sibling x402 docs site. Compute-market pricing belongs at Compute Market. This desk owns the finance loop — how value is held, moved, limited, and accounted for — and it stops before advice.
FAQ
How do autonomous agents hold, move, and manage value?
They hold value as delegated operational authority — a wallet, virtual card, or payment token — not as legal ownership. They move it on a rail (x402, card issuing, AP2/ACP, transfer) only after a policy check on amount, counterparty, purpose, time, and owner. They manage it by writing intent, authorization, settlement, fees, refunds, and denials into a ledger that does not depend on the model’s memory.
Is the Treasury Desk financial advice?
No. Agent Capital is an independent educational publication. The desk is a teaching blotter. Teaching amounts are illustrative props, not quotes, protocol fees, or recommendations to buy, hold, or use any asset, wallet, or rail.
What is a teaching ticket?
A labeled, synthetic blotter item authored by Agent Capital. Counterparties use the reserved .example TLD. Dollar and cent figures are props so the stations are visible. Rails, control types, and protocol roles are taken from primary documentation cited on the page.
Why does a denied payment still get a ledger line?
Because the attempt is the incident. A dashboard of settled payments cannot show prompt injection that almost became a transfer. Failed authorizations, invalid signatures, and blocked counterparties belong in the same event model as captures and refunds.
How is this different from the treasury-and-accounting guide?
The guide is the event model and reconciliation table. The Treasury Desk is the characteristic walkthrough: one ticket, six stations, sourced, interactive. Use the desk to see the loop; use the guide to implement the ledger.
Cite teaching tickets as illustrative artifacts authored by Agent Capital on 2026-09-19, never as observed payments, quotes, or protocol benchmarks. Independent educational publication. Not financial, legal, tax, accounting, custody, or investment advice.
Source
Coinbase Developer Platform: Agentic Wallet overview
Defines Agentic Wallet as tools for agents to hold, spend, trade, and earn stablecoins with guardrails.
Source
Coinbase Developer Platform: Agentic Wallet CLI
Documents CLI and MCP wallet capabilities, x402 use cases, per-session caps, and per-transaction limits.
Source
Coinbase Developer Platform: AgentKit wallet management
Describes AgentKit wallet providers, default CDP non-custodial wallet support, and wallet operations.
Source
Coinbase Developer Platform: x402 wallet role
Explains wallets as payment mechanisms and identifiers in x402.
Source
x402 Docs: introduction
Explains x402 as an HTTP 402-based payment standard for APIs and content.
Source
x402 Foundation GitHub
States x402 principles and its network, token, and currency-agnostic direction.