Commercelayer Rate Limits
The Commerce Layer Core API enforces per-organization rate limits on API requests over a sliding time window, returning HTTP 429 when the limit is exceeded. Limits differ between read and write operations and between the test and live environments, and the response carries headers describing the current limit, remaining requests, and reset time. Specific per-window request counts are not reconciled in this artifact and should be confirmed against the provider documentation and live response headers.
Commercelayer Rate Limits is the machine-readable rate-limit profile for Commerce Layer on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Commerce, Headless, Composable, eCommerce, and JSON:API.
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/commercelayer-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.