Each part is tagged: Available where it ships today, Coming where it doesn’t yet.
Illustrative, not a product screenshot.
Whoever calls, your systems, your own agent, or an agent on the network, works against the same transaction context, inside the same permissions, and leaves a record on it.
A key acts as your organization and only ever sees your side of a connection. Everything it reads or writes is the same record Workspace shows your team and Gio reasons over.
Documents, payments, and treasury over one org-scoped contract, with document writes where your environment has them enabled.
The Rivet MCP server runs beside your agent and turns the contract into MCP tools, one per operation, acting as your organization with the scopes of the key you give it.
Gio and other agents find what providers offer, pay per call over x402 within your policy, and bring the answer back to the transaction it was for.
Who did what, when, with what evidence: verified on every read, attributed down to the key, and exported as a bundle anyone can check offline without trusting Rivet.
x402 puts the price in the HTTP response. The Context API puts the transaction around it: who is asking, for which transaction, under what authority, and where the record goes.
INV-4417’s freight line, $1,240.00, is waiting on proof of delivery.
As gio.carmony@rivet.network, attached to INV-4417. Tamarack Freight’s endpoint answers 402 with its terms.
All four, or Jordan Kim decides.
0.05 USDC from Carmony’s Rivet wallet. The retry carries the signed payment in PAYMENT-SIGNATURE.
The signed proof of delivery attaches to INV-4417, each side gets one ledger line, and Jordan approves the freight line.
HTTP/1.1 402 Payment Required
PAYMENT-REQUIRED: eyJ4NDAyVmVyc2lvbiI6Miwi…
# PAYMENT-REQUIRED, decoded
{
"x402Version": 2,
"resource": {
"url": "https://api.provider.example/pod/SHP-77120",
"description": "Signed proof of delivery",
"mimeType": "application/json"
},
"accepts": [{
"scheme": "exact",
"network": "eip155:8453",
"amount": "50000",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"payTo": "0x4b1e…9c07",
"maxTimeoutSeconds": 60,
"extra": { "name": "USD Coin", "version": "2" }
}]
}GET /pod/SHP-77120
PAYMENT-SIGNATURE: eyJ4NDAyVmVyc2lvbiI6Miwi…
HTTP/1.1 200 OK
PAYMENT-RESPONSE: eyJzdWNjZXNzIjp0cnVlLCJ0…The wire is open x402, version 2, the one Rivet’s pay-by-agent guide documents. The Context API’s part is around it: the authority check before Gio pays, and the ledger line after.
A carrier, a manufacturer, a credit bureau: each holds context a transaction needs. Publish it once as a priced resource and Gio can use it for the businesses on the network. No payment system to build, no agent accounts, no connector to build per customer.
Whether this agent may buy this, for this transaction, under its business’s policy.
Priced in dollars, settled in USDC per request, swept to your treasury on your schedule.
Every call names a verified business, a person, and an agent.
Each request arrives attached to its transaction: the connection, the document, the workflow step.
One ledger line per request on both sides, exportable.
There is no separate developer account. A key acts as your organization, and an admin mints it in Settings → Developers.Providers: tell us what you’d publish, and we’ll set you up as the agent surface opens. Partner with Rivet →