Chord · Rate Limits
Chord Commerce Rate Limits
Chord Commerce Rate Limits is the rate-limit profile for Chord on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Tagged areas include Commerce, Composable Commerce, Headless Commerce, Order Management, and OMS.
0 Limits
Transcribed from the provider's documentation on 2026-08-13 — docs.chord.co/server-events-overview, docs.chord.co/audie....
View Source
Limits
Chord publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Chord publishes NO rate limits for any of its three API surfaces. There is no limits page, no per-key/per-account quota, no burst allowance, and no X-RateLimit-*/RateLimit-*/Retry-After header documented for /api/track, /api/identify, /audiences or the MCP endpoint. An agent integrating with Chord therefore has no runtime signal to back off on and no documented ceiling to design against — it can only observe failures. The one place rate limiting IS documented is the opposite direction: when a DESTINATION rate-limits Chord, Chord classifies that as a recoverable error and re-queues the event with exponential backoff (3 attempts, 10-minute base, capped at 24 hours), then dead-letters it. That is Chord consuming someone else's limit, not publishing its own.
CommerceComposable CommerceHeadless CommerceOrder ManagementOMSCustomer Data PlatformCDPEvent TrackingCommerce AnalyticsCustomer Lifetime ValueAI AgentsCommerce CopilotSolidusSpreeRuby on RailsShopifyDirect to Consumer
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.