Hatchet Rate Limits
Rate, throughput, and quota policies for Hatchet Cloud and the open-source Hatchet engine. Cloud throughput limits are sourced from hatchet.run/pricing (Team tier 500 RPS, Enterprise sustained 300M+ runs/month). Engine-level rate-limit primitives are part of the Hatchet API surface itself (the /tenants/{tenant}/rate-limits endpoints) and apply to task execution, not HTTP requests.
Hatchet Rate Limits is the machine-readable rate-limit profile for Hatchet on the APIs.io network, in the API Commons Rate Limits shape.
It captures 6 rate-limit definitions, across the developer, team, scale, enterprise, and self-hosted tiers, measuring requests_per_second and task_runs_per_month.
Limit state is signalled in the limit, remaining, reset, and retryAfter response headers, and an exhausted limit returns HTTP 429.
This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.
The profile also includes 6 backoff/retry policies defined and response codes documented for throttled, quotaExceeded, and serviceUnavailable.
Tagged areas include Task Queue, Workflow Engine, Durable Execution, Rate Limiting, and Throughput.
limitremainingresetretryAfter
generated, dated 2026-05-25.
Limits
Policies
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.