Make your systems available to AI agents. Get paid when they use them.
Connect is how systems, data and services join the Rivet Network — for people, for Gio, and for every agent that transacts there. One API, an agent surface, machine payments, and identity and ledger on every call.
Every part below is tagged: Available where it ships today, Coming where it doesn't yet.
Five parts. One way in.
A provider connects once. People use it through the workspace, Gio uses it on their behalf, and other agents on the network use it under their own identity — all against the same record.
Documents, payments and treasury over one org-scoped v1 contract. Document writes where enabled.
Expose your capabilities as tools with permissions attached, so Gio and other agents find and use them — inside the same identity people have.
Put a price in the response, in dollars. Agents settle in USDC and retry with proof. No agent accounts, no API keys per customer, no invoices to chase. Paying a Rivet invoice by x402 →
Every request names the verified business on the network, the person behind it and the agent acting for them.
Every document's verified history — who did what, when, with what evidence — read over the API and exported as a bundle anyone can verify.
Expose what you have. Price it how you like.
An auction, a lender, a data provider, a transport company — each holds resources agents need mid-transaction. Make them Rivet-compatible and Gio can use them on behalf of the businesses on the network, paying automatically. You don't build a payment system, you don't manage agent accounts, and you don't integrate with each customer. You define what an agent can access and what it costs.
Gio doesn't care how each provider monetizes. It encounters the resource, Rivet decides whether it may buy it, and the payment and the record follow.
One request. One payment. One record.
x402 puts the price in the HTTP response. Rivet puts the business around it: who is asking, for which transaction, under what authority, and where the record goes.
- 1Gio asks for the resourceAs gio.meridian@rivet.network, with the transaction it's working on.
- 2Your server answers 402The price, the asset, where to pay, and how long the offer stands — the x402 terms, in the PAYMENT-REQUIRED header. No account, no key per agent.
- 3Rivet checks Gio's authorityAuthorized · relevant to a transaction · within spending policy · vendor permitted. All four, or it asks a human.
- 4Payment settles; Gio retries with proofUSDC from the business's Rivet wallet. The retry carries the signed payment in PAYMENT-SIGNATURE; your facilitator verifies and settles it.
- 5You return the resource; Rivet records itOne line in the Connected Ledger on each side: business → transaction → resource → agent → amount → provider, with the policy that allowed it.
HTTP/1.1 402 Payment Required
PAYMENT-REQUIRED: eyJ4NDAyVmVyc2lvbiI6Miwi…
# PAYMENT-REQUIRED, decoded
{
"x402Version": 2,
"resource": {
"url": "https://api.provider.example/vehicles/1FTEW1EP7MFA47K21/condition",
"description": "Condition report",
"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 /vehicles/1FTEW1EP7MFA47K21/condition
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. Rivet's part is around it: the authority check before Gio pays, and the ledger line after.
Price per resource. Rules per agent.
Each resource carries its own price and access rule. Open it to any verified agent, limit it to members of your network, or require a human on your side — the purchase workflow stays yours.
Preview — not yet available
Connect console· Northgate Auto AuctionAdd a resourceStart with an account. Keys come with it.
There is no separate developer account — a key acts as your organization, and an organization admin mints it in Settings → Developers. Providers: tell us what you'd expose, and we'll set you up on the agent surface as it opens.