Gelato Rate Limits
The Gelato API is authenticated per account with an X-API-KEY and is served over HTTPS across the order, product, shipment, and ecommerce subdomains. Gelato applies request throttling to protect its platform, but specific per-endpoint request-per-minute or per-day limits are not published in the public API documentation and are not reconciled in this artifact.
Gelato Rate Limits is the machine-readable rate-limit profile for Gelato on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Print on Demand, Ecommerce, Fulfillment, Distributed Production, and Rate Limiting.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/gelato-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.