Skip to main content
Limits apply per minute or per 15-minute window. Higher plans raise API call throughput.

​
Limits by tier

New-proof, sign-in, and status limits are the same on every plan. API call throughput is where higher plans scale.

​
When you hit a limit

APIs return 429 Too Many Requests. Honor these response headers before retrying: CORS exposes Retry-After, RateLimit, and RateLimit-Policy so browsers and agents can read them.
  • Exponential backoff: wait, then double the wait on each retry.
  • Creates: confirm the first request failed before sending another. A duplicate proof costs credits.
  • Polling: wait a few seconds between polls. Back off on errors.

​
Tips

  • Reuse proofs. Checking an existing proof is free. Creating a new one costs 4 to 73 credits and counts against the verification window, so cache the proof ID and check it.
  • Check before you create. Use gateCheck with your gateId for access decisions. It reads saved proofs, so you create a new proof only for a missing check.
  • Need higher limits? Pro raises API throughput four times. Enterprise raises it ten times, by agreement. See Pricing.

​
402 and credits

When credits run out, billable calls return 402 Payment Required with a quote, not 429. Pay for the call with x402, no account needed, or add credits and retry. Next: SDK errors
Last modified on October 25, 2026