ZeroDev · Rate Limits

Zerodev Rate Limits

ZeroDev meters its bundler and paymaster RPCs primarily by a per-plan Credit pool (consumed by UserOperations and infra calls) and by an included gas-sponsorship budget, rather than by published fixed per-second request rates. RPC throughput limits exist per project and plan and are enforced by the meta-infrastructure; specific per-method request-per-second values are not published and are not reconciled in this artifact. Sponsorship policies on the paymaster (per-app, per-user, per-UserOp caps) act as the primary throttle on gas spend.

Zerodev Rate Limits is the machine-readable rate-limit profile for ZeroDev on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring credits, usd_gas, requests, and sponsorships.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Account Abstraction, ERC-4337, Paymaster, Bundler, and JSON-RPC.

4 Limits Throttle: 429
Account AbstractionERC-4337PaymasterBundlerJSON-RPCRate LimitingQuotasThrottling

Limits

Credits Per Month project
credits
see plan (10K Developer / 100K Growth / 1M Scale / custom Enterprise)
UserOperations and infra calls draw down the plan Credit pool.
Gas Sponsorship Budget project
usd_gas
see plan (up to $250 Growth / up to $1,000 Scale / custom Enterprise)
Included gas-sponsorship allowance; further sponsored gas is billed/topped up.
RPC Throughput project
requests
see provider documentation
Per-project bundler/paymaster RPC throughput; specific RPS values not published.
Paymaster Sponsorship Policy Caps project
sponsorships
configurable
Per-app / per-user / per-UserOp sponsorship caps configured in the dashboard.

Policies

Credit-Metered Plans
Each plan includes a Credit pool; overage is handled by upgrading plan or top-up.
Sponsorship Gating
Paymaster sponsorship is governed by configurable policies that cap which UserOps are sponsored.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 and honor Retry-After.

Sources