Zeabur · Rate Limits

Zeabur Rate Limits

Zeabur's public GraphQL API (https://api.zeabur.com/graphql) is authenticated per API key with Bearer tokens. Zeabur does not publish specific numeric request-per-minute limits for the GraphQL API in its documentation; abusive or excessive request volume may be throttled. Practical throughput is also bounded by plan-level resource quotas (compute, memory, bandwidth, number of projects/services) rather than by a documented API call ceiling. GraphQL subscriptions run over a WebSocket connection (wss://api.zeabur.com/graphql) using the graphql-ws protocol.

Zeabur Rate Limits is the machine-readable rate-limit profile for Zeabur on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring requests, resources, and connections.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include PaaS, Deployment, Cloud, DevOps, and GraphQL.

3 Limits Throttle: 429
PaaSDeploymentCloudDevOpsGraphQLRate LimitingQuotasThrottling

Limits

GraphQL Requests api_key
requests
see provider documentation
No documented per-minute numeric limit; excessive volume may be throttled. Requests are authenticated per API key with a Bearer token.
Plan Resource Quotas account
resources
plan-dependent
Compute (vCPU), memory, bandwidth, and project/service counts are bounded by the subscribed plan (Free Trial / Developer / Team) rather than by an API call ceiling.
WebSocket Subscriptions api_key
connections
see provider documentation
Real-time build/runtime log subscriptions use graphql-ws over wss://api.zeabur.com/graphql; connection limits are not documented.

Policies

Bearer Authentication
Every request must carry an Authorization Bearer API token; revoked keys are rejected immediately.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 and honor any Retry-After header.
Resource-Bound Throughput
Effective usage is governed by plan resource quotas; upgrade the plan to raise compute/bandwidth ceilings.

Sources

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.
All 92 tools

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/zeabur-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.