Estuary Rate Limits
The Estuary Flow control plane is a Supabase/PostgREST deployment; Estuary does not publish explicit numeric request-per-minute limits for the control-plane REST API. Practical constraints are shaped by access-token expiry, PostgREST result paging, and per-tenant catalog quotas on the number of tasks and collections rather than by an HTTP call-rate ceiling. The data plane itself is governed by tenant task/collection quotas and connector instance counts, not by API request rate.
Estuary Rate Limits is the machine-readable rate-limit profile for Estuary on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 5 rate-limit definitions, measuring requests, seconds, tasks, collections, and rows.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Data Integration, Streaming ETL, Change Data Capture, CDC, and Real-Time Data.
Limits
Policies
Sources
- https://docs.estuary.dev/reference/authentication/
- https://docs.estuary.dev/getting-started/pricing/
- https://docs.estuary.dev/concepts/
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/estuary-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.