Limits by tier
Limits scale with your plan. Verification and sign-in have tighter windows because they run real checks.
Verification and sign-in limits are the same across tiers. A check is a check regardless of plan. API call throughput is where higher tiers 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: do not blind-retry. Confirm the first request did not succeed before sending another. A duplicate proof costs credits.
- Polling: wait a few seconds between polls. Back off on errors.
Tips
- Reuse proofs. A gate check (1 credit) reads an existing proof. Creating a new one (4 to 73 credits) is heavier and counts against the verification window. Cache the proof ID and check it instead.
- Gate checks, not raw verification. Use
gateCheckwith yourgateIdfor access decisions. It reads saved results first and only creates a new proof when needed. - Need higher limits? Pro raises API throughput four times. Enterprise raises it ten times, with service levels and custom packages. See Pricing.