Limits by tier
Sign-in and status limits are the same on every plan. API calls and new proofs scale with the plan. Pro is 4× the free budget and Enterprise is 10×. The budget belongs to the caller who pays. A signed-in account or access key is counted on its own wallet even when it writes into a delegated agent’s vault, and a wallet-signed request with no session is counted on the wallet that signed it. Limits are counted once across the whole service, not per server.
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 new-proof budget, so cache the proof ID and check it.
- Check before you create. Use
gateCheckwith yourgateIdfor access decisions. It reads saved proofs, so you create a new proof only for a missing check. - Need higher limits? Pro raises both budgets four times. Enterprise raises them ten times, by agreement. See Pricing.