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.
Limits
Policies
Sources
- https://zerodev.app/pricing
- https://docs.zerodev.app/meta-infra/rpcs
- https://docs.zerodev.app/sdk/core-api/sponsor-gas
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for rate limits
4 MCP tools reach this
find_rate_limitsBrowse and filter every rate limit in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/zerodev-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.