Monetization Gateway
Monetization Gateway
Charge for access to an API, a piece of content, a dataset, or a tool on each HTTP request.
What it is
Monetization Gateway is how AZPay puts a price on an HTTP resource. The publisher of the API, content, dataset, or MCP tool sets the charge. The consumer — a person or an agent — pays to receive that resource.
How it works
- The published path is short.
- The client requests the resource.
- The gateway answers 402 Payment Required with the payment options.
- The client pays and retries the request with proof.
- The facilitator verifies that proof.
- When verification is accepted, the resource answers 200.
Status 402 is part of HTTP and is described in RFC 9110. x402 uses that response to negotiate payment before the resource is delivered. RFC 9110.
Where it fits
- APIs billed per call
- Content released after payment
- Datasets
- MCP tools exposed to agents
What is available
The public demo runs on testnet. Pix payout to the merchant is available. This page does not describe general availability or mainnet operation.