Surrealdb Rate Limits
SurrealDB does not publish explicit rate limits for its HTTP REST API in its public documentation as of June 2026. Native rate limiting is a tracked feature request (GitHub issue #2016) rather than a shipped capability. For SurrealDB Cloud, connection and query concurrency are governed by the compute tier provisioned. Operators running self-hosted deployments are advised to implement rate limiting at the reverse proxy layer. The standard HTTP 429 status code is returned by the infrastructure layer when limits are exceeded.
Surrealdb Rate Limits is the machine-readable rate-limit profile for SurrealDB on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 1 rate-limit definition, measuring requests_per_minute.
The profile also includes response codes documented for throttled.
Tagged areas include Rate Limiting and SurrealDB.
Limits
Sources
- https://surrealdb.com/docs/surrealdb/integration/http
- https://github.com/surrealdb/surrealdb/issues/2016
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/surrealdb-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.