Skip to main content

Payment is authentication

Public pay-per-query access requires no account or API key. A paid request carries the appropriate proof of payment:
  • x402: a signed USDC transfer authorization, verified before the answer is returned.
  • MPP/Tempo: a signed Tempo charge credential, verified the same way.
Retry the same request that returned the challenge. Do not reuse payment credentials for a different request or assume a fresh payment is safe after a timeout. See payment retry behavior.

Limits

  • Paid routes: no per-wallet request cap; the price of each call is the throttle. Under heavy load the API may answer 503 SERVICE_UNAVAILABLE with a Retry-After header. Nothing ran and nothing is billed, so retry after the delay.
  • Free catalog routes (/v1/public/*): 180 requests per minute per IP address (IPv6 addresses count per /64). Over the limit, you get 429 RATE_LIMITED with a Retry-After header giving the seconds to wait.
Responses carry X-RateLimit-Limit and X-RateLimit-Remaining where a limit applies. Need a higher budget? Get in touch.

In practice

  • No API key to provision for the public paid surface.
  • Lose the wallet, lose the funds. Treat it like any other production secret, and use a dedicated agent wallet with a small balance.