{"currency":"USDC","token_contract":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","decimals":6,"network":{"name":"base-mainnet","chain_id":8453},"unit":"one HTTP request to /api/v1/protected-data","price_per_request":"0.01","price_per_request_units":"10000","no_subscription":true,"no_minimum":true,"billing":"Per call. Only a response that delivers the data (HTTP 200) is billable, and nothing is charged for a 402 or another 4xx. A 503 can be returned after a payment has already settled; its body states whether the data was delivered and what happens next. If a payment settled and you did not receive the data, whatever the status code, contact the operator (see /legal) with the tx_hash.","payment_schemes":["exact"],"gas":{"exact":"The gateway pays the settlement gas. You pay only the quoted USDC."},"refunds":{"freshness_sla_seconds":900,"policy":"If the data is staler than the freshness SLA you are not charged for it: the call is either refused before delivery (HTTP 503) or the price is credited to your non-refundable, non-transferable account balance at this gateway, spendable only via X-Account-* vouchers. The test is elapsed seconds only — no discretion, no dispute.","duplicate_payments":"A payment authorization is single-use, and re-presenting one already used for a purchase here charges nothing by itself. While it still matches the current price and receiving address, re-presenting it returns 409 (authorization_already_used); if either has changed since your purchase, you get a 402 instead — the new authorization it asks for would be a new purchase, so do not sign one to recover an earlier purchase; contact the operator instead (see below). Adding a re-delivery signature from the paying address (see the 409 body) returns, at no charge, that purchase's data as stored at purchase time, for as long as that stored copy is kept; a signature that fails this check gets 403 and no data. If this gateway attempted to settle an authorization and could not confirm the result (503 settlement_unconfirmed), re-present the same authorization at the same endpoint: once the gateway finds that attempt's payment on-chain, it delivers the data without a new charge (while the data is staler than the freshness SLA, the freshness policy above applies instead). A payment to the receiving address that this gateway did not attempt to settle is not delivered automatically, whether the authorization is presented during or after its validity window: it gets a 503 without the data (normally paid_not_recorded_here). If you paid this gateway for data and did not receive it, contact the operator (see /legal) with the tx_hash; a person will check it."},"tax":"The price includes any applicable Japanese consumption tax.","business_use_only":true,"free":["402 challenge with a real data preview","/stats","/.well-known/x402","/llms.txt","/client.py","/mcp-server.py","/verify-receipt"],"terms":"https://pay.obolpay.xyz/terms","legal":"https://pay.obolpay.xyz/legal","privacy":"https://pay.obolpay.xyz/privacy"}