PILOT / WALLETSETTLED
✓
PAYMENT CONFIRMED42.00 USDC
Compute reservation · job #8F42
- Buyer
- agent-research
- Counterparty
- compute-east
- Mandate
- compute / max 50
- Network
- Base
- Transaction
- 0x71…9ac2
A shopping agent needs a mandate.
Not a blank check.
Bind the counterparty, request, spending boundary, transfer, and verification into one inspectable exchange so an agent can transact without becoming an unrestricted wallet.
No invisible authorityNo unbounded balanceNo anonymous counterparty
Authority is a data structure.
Make it narrow.
Agent commerce introduces questions about who requested the action, what was approved, how much may be spent, and whether settlement occurred. Pilot’s current wallet surface supports bounded payment operations and verification, while the network supplies persistent identities and signed requests around the workflow. Higher-order enterprise approval lifecycle remains a separate productization track.
Allowed purposeIsolated compute
Per-transaction limit≤ 50 USDC
Approved recipients2 service agents
Human reviewAbove 35 USDC
Expires24 hours
A persistent network counterparty
Pilot peers communicate through signed identities and explicit trust relationships rather than anonymous endpoints.
A guarded wallet with spend limits
Wallet exposes request, payment, balance, and verification methods with configurable spending boundaries.
Check settlement programmatically
The workflow can validate payment state before continuing to delivery or the next business action.
Request. Check. Settle. Release.
- 01→
Establish the counterparties
Resolve and trust the agents participating in the exchange.
- 02→
Create the payment request
Bind the amount and destination to the workflow’s business context.
- 03→
Apply the wallet boundary
Keep the requested action inside the configured spend limit and guarded app grants.
- 04✓
Verify before continuing
Confirm the transfer state programmatically before goods, data, or service access changes hands.
Payment mandate canvasDefine what the agent may buy
Define what the agent may buy
before it holds a wallet.
Describe the exchange and boundary. We will map counterparties, payment request, spend cap, settlement evidence, and the point where human approval belongs.
What you get
- 01Counterparty and trust model
- 02Spend boundary
- 03Verification and release sequence
Technical basis
Specific product surfaces.
Inspectable in the docs.
- 01Guarded local wallet app
- 02USDC on Base, Ethereum, and Polygon
- 03Payment request and verification methods
- 04Per-wallet spending limits