Zambo guide
x402 API Payments
x402 is an HTTP payment pattern that lets an API request return payment instructions instead of a normal response.
Add Zambo to your AIThe request and response
- The client requests a protected resource.
- The server returns payment instructions instead of the resource.
- The wallet reviews and authorizes the payment.
- The client retries the request and inspects the response.
The payment response and the returned work should be checked separately.
What an API client must support
The client needs to understand the payment challenge, use a wallet and network it supports, and resume the same request after payment. A service can still refuse or fail the underlying call, so inspect its response separately.
Check the current client and server documentation before enabling unattended payment.
Payments and work records are separate
The payment challenge describes the request and the amount due. A separate work receipt records the tool call and its returned status; it should not be treated as a wallet settlement confirmation.
Open the saved call at the receipt checker to inspect its recorded fields.
Try this prompt
Start with a small request. Change the details to match your task.
Use Zambo to explain the payment step before it happens, then show the receipt for the completed request.
FAQ
What is x402 API payments?
x402 is an HTTP payment pattern that lets an API request return payment instructions instead of a normal response.
What does a Zambo receipt show?
It shows the saved record and its available status. It does not prove that the output is correct or complete.
How do I try this with Zambo?
Check the payment request in your wallet, approve only a request you intend to pay, then review the resulting receipt.
Try it with your AI
Connect Zambo once, then ask your AI to use it for a real task.
Add Zambo to your AI Try Zambo Chat