Gcore Rate Limits
Gcore applies per-service rate limits on its unified REST API at api.gcore.com. The Streaming API documents a general limit of about four requests per second; the CDN purge operation is constrained to one "purge all" request per CDN resource per minute and two "purge by URL" requests per resource per minute, with a single URL purge limited to 100 URLs and a single pattern purge limited to 10 patterns. Cloud, DNS, Storage, WAAP, Inference, and FastEdge enforce their own per-account quotas and request limits that are not fully enumerated in public docs. Specific values beyond the ones noted here are not reconciled in this artifact.
Gcore Rate Limits is the machine-readable rate-limit profile for Gcore on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 6 rate-limit definitions, measuring requests.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Edge Cloud, CDN, Streaming, Edge AI, and Infrastructure.
Limits
Policies
Sources
- https://gcore.com/docs/api-reference/overview
- https://gcore.com/docs/streaming-platform/api/streaming-platform-api-tutorial
- https://gcore.com/docs/cdn
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/gcore-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.