Sieve Rate Limits
Sieve throttles primarily by concurrency rather than per-minute request counts. Jobs are submitted asynchronously to the Push endpoint and queued; the number of jobs that run in parallel is bounded by the account's concurrent request limit (up to 3 on the Starter plan, custom on Production). Excess jobs queue rather than fail. Specific HTTP rate limits on the management endpoints are not separately reconciled in this artifact.
Sieve Rate Limits is the machine-readable rate-limit profile for Sieve on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring concurrent_requests and jobs.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include AI, Video, Audio, Media Processing, and Async Jobs.
Limits
Policies
Sources
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/sieve-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.