specification: API Commons Rate Limits specificationVersion: '0.1' schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits provider: Fox Factory Holding providerId: fox-factory-holding created: '2026-05-04' modified: '2026-09-14' generated: '2026-09-14' method: searched source: https://ridefox.com/llms.txt (HTTP 200, 2026-09-14) plus live header observation on https://ridefox.com/api/ucp/mcp reconciled: true tags: - Rate Limiting - Commerce - MCP description: >- Fox Factory Holding's one callable surface — the UCP/MCP commerce endpoint at https://ridefox.com/api/ucp/mcp — is rate limited per source IP. The provider states the policy and the exhaustion status code in its published agent instructions but publishes no numeric limit, and no RateLimit-* or Retry-After header appeared on the successful responses we observed. notes: >- Upgraded 2026-09-14 from a 2026-05-04 bulk-sweep scaffold that recorded "no public API". That scaffold was wrong: a live, anonymous MCP endpoint is served and its rate-limit policy is documented. limit_count is 1 because exactly one limit is published; its numeric value is not. sources: - https://ridefox.com/llms.txt - https://ridefox.com/robots.txt headers: requestId: x-request-id apiVersion: x-shopify-ucp-mcp-api-version rateLimit: null retryAfter: null responseCodes: throttled: 429 limit_count: 1 limits: - name: UCP/MCP endpoint requests scope: per-ip metric: requests limit: undisclosed timeFrame: undisclosed burst: null endpoint: https://ridefox.com/api/ucp/mcp status_on_exhaustion: 429 source: https://ridefox.com/llms.txt note: >- Provider text: "Respect rate limits. The MCP endpoint is rate-limited per IP. Back off on 429 responses." No number, window or Retry-After value is published. policies: - name: Back off on 429 description: Agents are instructed to back off when the endpoint returns 429. No retry schedule is specified. source: https://ridefox.com/llms.txt - name: No published numeric quota description: >- Neither the storefront nor the merchant profile at /.well-known/ucp states a request-per-second or per-minute allowance, so a consumer cannot size a workload in advance. - name: No runtime rate-limit headers observed description: >- Successful tools/list responses carried x-request-id and x-shopify-ucp-mcp-api-version but no RateLimit-*, X-RateLimit-* or Retry-After header, so an agent learns its budget only by being throttled. maintainers: - FN: Kin Lane email: kin@apievangelist.com