Buy from any Veto merchant.
The canonical guide for autonomous agents. Discover a merchant's manifest, present a checkout, get a signed receipt, and settle on-chain. Open to all agents – no Veto account required.
Veto governs · the rail executes.
# 1 · discover the merchant storefront manifest# (exact paths & schema are in the docs – never assume)curl -s https://<merchant-host>/.well-known/agentic-checkout.json# → catalog, accepted rails, and how to present a checkout
The flow
Four steps from discovery to settlement
A merchant publishes a signed manifest; you discover it, present a checkout, and settle on-chain. Veto verifies the buyer and runs the merchant's acceptance policy in between.
Discover the manifest
Fetch the merchant's storefront manifest at /.well-known/agentic-checkout.json. It declares the catalog, accepted rails, and how to present a checkout – a machine-readable contract you read without scraping.
Present a checkout
Send a cart plus an optional signed mandate and an intent describing the purchase. The mandate is optional and polymorphic – veto, ap2, acp, or none.
Get a signed receipt
Veto verifies the buyer (authorization, reputation, screening), runs the merchant's acceptance policy, and returns a verdict – allow, deny, or escalate – with a signed, non-repudiable receipt on every accepted sale.
Settle on-chain
On an allow, settle on-rail – x402 / USDC on Base today. Funds go directly to the merchant's wallet; Veto is non-custodial and never holds them.
Rails
Rail-agnostic settlement
x402 / USDC on Base is live today – real settlement, proven end to end. Veto is rail-agnostic by design: additional rails (such as MPP via Tempo / Stripe) are additive, not a rewrite. The verdict and the signed receipt are the same regardless of how the money moves.
Why buy through Veto
Verified merchants, signed receipts, final settlement
Built for autonomous flows: you know who you're paying, you get cryptographic proof of every purchase, and outcomes are deterministic.
Verified merchants
Every storefront is a real, screened merchant with a signed manifest – not an unverified endpoint. You know who you are paying before funds move.
Signed, non-repudiable receipts
Each accepted sale ships with an Ed25519 receipt you (or anyone) can verify offline against the merchant’s JWKS. Cryptographic proof of the purchase, not a log line.
No chargebacks
On-chain settlement is final. A confirmed payment can’t be reversed or disputed after the fact – clean, deterministic outcomes for autonomous flows.
Open to all agents
No Veto account required to buy. A mandate is optional and works with veto / ap2 / acp – bring your own authorization scheme, or none at all.
A mandate is optional. Veto is open to all agents and does not require its own authorization scheme. Mandate types are polymorphic – veto, ap2, acp, or none. Bring a signed mandate as an optional fast-lane, or present a checkout without one and let the merchant's policy decide.
Reference
Read these next
Exact endpoints, the manifest schema, and receipt verification live in the docs. Do not assume endpoint paths – read the docs.
