generated: '2026-08-26'
method: searched
source: https://shop.oatside.com/agents.md
api: Oatside SG Storefront UCP / MCP
limit_count: 0
rate_limits:
- scope: per-ip
  surface: https://shop.oatside.com/api/ucp/mcp
  limit: null
  window: null
  burst: null
  status_on_exhaustion: 429
  guidance: Back off on 429 responses.
  documented_quote: 'Respect rate limits. The MCP endpoint is rate-limited per IP. Back off on 429 responses.'
  source: https://shop.oatside.com/agents.md
response_headers:
  observed: []
  note: >-
    No RateLimit-*, X-RateLimit-* or Retry-After header appeared on a live HTTP 200
    tools/list response on 2026-08-26. Only x-shopify-ucp-mcp-api-version and x-request-id
    were returned. An agent therefore has no pre-exhaustion runtime signal and can only
    react after receiving a 429.
notes:
- limit_count is 0 because the provider documents that a per-IP limit exists and names the
  429 status, but publishes no number, window or burst allowance. The qualitative limit is
  recorded above so the gap is visible rather than absent.
- No rate limit was deliberately triggered; probing to exhaustion against a live consumer
  storefront is out of bounds for this pipeline.