Edgedb Rate Limits
EdgeDB/Gel does not publish explicit rate limits for its HTTP EdgeQL or GraphQL APIs in its public documentation as of June 2026. The HTTP API enforces a single-query-per-request constraint and does not support DDL or transaction commands. Connection and query throughput are constrained by the compute unit size of the provisioned instance. Standard HTTP 429 Too Many Requests responses apply if limits are enforced server-side.
Edgedb Rate Limits is the machine-readable rate-limit profile for EdgeDB on the APIs.io network, in the API Commons Rate Limits shape.
It captures 2 rate-limit definitions, measuring queries_per_request and connections.
Limit state is signalled in the retryAfter response header, 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 response codes documented for throttled.
Tagged areas include Rate Limiting, Database, and HTTP API.
retryAfter
generated, dated 2026-06-12.
Limits
Sources
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.