x402 payments
Make every API request an opportunity.
Charge applications and AI agents for access to your APIs, data and digital services using stablecoin payments over HTTP.
The request flow
GET /your-resourceA client requests your paid resource402 Payment RequiredYour server returns the payment termsPayment verified → 200 OKGrant access after settlement is confirmed
Paid access.
Part of the request.
Give compatible applications and AI agents a way to pay for each resource they use.
GET /your-resourceThe client asks for a paid resource.
APIs · Datasets · Digital content · Compute
Read the integration guideSet your terms
Configure the resource, price and supported payment parameters in your integration.
Request payment
Return an HTTP 402 response. The client authorises payment and retries with its payment payload.
Deliver the resource
Verify and settle the payment through Ivorypay, then return your response.
A few useful answers.
What can I charge for?
API calls, datasets, digital content and compute access are examples. Your server decides which resources require payment.
Does every client support x402?
Clients need to understand the payment requirements and authorise a supported stablecoin payment. See the integration documentation for the supported flow.
When should I return the paid resource?
After the payment has been verified and settlement confirmed. A submitted payment payload alone is not a successful payment.
Build your next payment flow.
Tell us how your business moves money.