generated: '2026-08-22'
method: probed
source: >-
  https://www.drinkhint.com/agents.md (published guidance) and response headers observed on
  https://www.drinkhint.com/api/ucp/mcp, 2026-08-22
summary: >-
  A rate limit is documented in prose but never quantified. The provider states the MCP endpoint is
  rate-limited per IP and that agents must back off on 429, but publishes no number, no window and
  no RateLimit-* headers. The only runtime cost signal returned is Shopify's complexity score.
limit_count: 0
limits: []
documented_but_unquantified:
- scope: per-ip
  surface: https://www.drinkhint.com/api/ucp/mcp
  window: not published
  limit: not published
  burst: not published
  statement: >-
    "Respect rate limits. The MCP endpoint is rate-limited per IP. Back off on 429 responses."
  source: https://www.drinkhint.com/agents.md
response_headers:
  standard_ratelimit_headers: false
  observed:
  - name: shopify-complexity-score
    example: '36'
    description: >-
      Query cost of the request as computed by the platform. Not a remaining-quota signal, but the
      only per-request cost number an agent can read.
  - name: shopify-complexity-score-v2
    example: '36'
  - name: x-request-id
    description: Per-request correlation id, useful when reporting a throttle.
  absent:
  - RateLimit-Limit
  - RateLimit-Remaining
  - RateLimit-Reset
  - X-RateLimit-Limit
  - X-RateLimit-Remaining
  - Retry-After
exhaustion:
  status: 429
  retry_after_header: not observed
  guidance: exponential backoff, per the published agent instructions
storefront_json:
  note: >-
    The read-only storefront JSON surfaces named in agents.md (/products/{handle}.json,
    /collections/{handle}/products.json, /search) carry no published limits either.
notes:
- limit_count is 0 because no numeric limit is published anywhere on a Hint host. An agent cannot
  compute a safe call rate from what is documented; it can only react to a 429 after the fact.