fabric · Rate Limits
Fabric Com Rate Limits
fabric does not publish per-endpoint rate limits on its public developer portal. The values below capture observable platform behavior and the conventions encoded in the v3 specs. Tenants requiring committed throughput negotiate it as part of their enterprise contract.
Fabric Com Rate Limits is the machine-readable rate-limit profile for fabric on the APIs.io network, conforming to the API Commons Rate Limits specification.
The profile also includes 5 backoff/retry policies defined.
Tagged areas include Commerce, Composable Commerce, Headless Commerce, E-Commerce, and Retail.
0 Limits
CommerceComposable CommerceHeadless CommerceE-CommerceRetailCartCatalogPIMOMSInventoryOffersPricingPromotionsCheckoutIdentityExperienceAgentic Commerce
Policies
All fabric v3 services are tenant-scoped. Request budgets are enforced per tenant access token rather than per-IP. fabric publicly reports 1B+ API calls/month served with sub-50ms latency, which sets the platform performance envelope.
Identity-issued bearer tokens enforce burst protection against mis-configured integrations. Servers return HTTP 429 with the standard `x-fabric-request-id` header for triage.
Cart Orchestrator (ShopperXP) calls fan out to Cart, Offers, and Inventory in a single shopper request. Clients SHOULD prefer the orchestrator over direct multi-service calls to remain within tenant throughput envelopes.
Experiences is served from `cdn.xm.fabric.inc` with CDN cache TTLs. Storefronts MUST treat reads as cached; cache-busting writes are not supported on this surface.
Product Agent runs are async with per-tenant concurrency caps. Clients MUST poll the run/job resource and accept queued runs during peak windows.
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.