Sieve · Rate Limits

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.

3 Limits Throttle: 429
AIVideoAudioMedia ProcessingAsync JobsRate LimitingQuotasThrottling

Limits

Concurrent Requests (Starter) account
concurrent_requests
3
Up to 3 jobs run in parallel on the Starter plan; additional jobs queue.
Concurrent Requests (Production) account
concurrent_requests
custom
Custom concurrency negotiated on the Production plan.
Job Queue account
jobs
queued
Jobs submitted above the concurrency limit are queued and processed as capacity frees up, rather than being rejected.

Policies

Concurrency-Based Throttling
Throughput is governed by concurrent request limits per plan; raise concurrency by upgrading to Production.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor Retry-After.
Asynchronous Submission
Push jobs and poll Get Job or use webhooks rather than blocking on synchronous responses.

Sources