DOCUMENTATION
Everything you need to build agent-native payments.
From your first paid request to production agent workflows.
ON THIS PAGE
Connect an agent, set a policy, and make a first paid request. The same request lifecycle carries through to production.
01
Create an API key
02
Define a spending policy
03
Make a paid request
04
Verify the receipt
A paid request begins when an agent discovers a priced endpoint. If payment is required, the server returns an authorization challenge. The agent evaluates the request against its policy, authorizes the payment, retries the request, and receives the resource together with a receipt.
01
Discover
02
Challenge
03
Authorize
04
Pay
05
Execute
06
Receipt
When payment is required, the endpoint returns a challenge. The agent pays within policy, retries, and receives the resource with a receipt.
REQUEST / HTTP
402 -> 200
POST /payments/authorize
Authorization: Bearer sk_live_8f42
Content-Type: application/json
{ "endpoint": "/v1/research", "budget": "0.10" }
RESPONSE / application/json
200 OK
{
"status": 200,
"settled": true,
"receipt": "rcpt_8H42"
}
Authorization ties the agent to a known identity and a policy before value moves.
Identity
Know which agent is making the request.
Budget
Set per-request and daily spend caps.
Policy
Limit destinations, services, and capabilities.
Approval
Require explicit review when a request exceeds policy.
Expose paid tools to agents with clear pricing, authorization, and receipts around each invocation.
Attach an agent wallet to a policy so payments remain within defined budgets and allowed services.
Subscribe to signed payment events and reconcile receipts with your application state.
A small set of predictable endpoints for payments, policies, and receipts.
POST
/payments
GET
/payments/:id
POST
/policies
GET
/receipts/:id