Skip to content
Error codes · Outages & the public API

RU-6004: Keyless MCP rate limited

Your address called the keyless MCP endpoint faster than its per-IP budget allows. This budget is deliberately tighter than the keyed one: a keyless call cannot be attributed to an account and, unlike the public outage JSON endpoint, an MCP response cannot be cached, so every call costs a fresh read.

On the wire

Ships with HTTP status 429, carrying "code": "RU-6004" in the response body alongside the human-readable error message. Existing fields are never replaced by the code: it is additive.

Common causes

  • An agent polling an outage tool in a loop instead of asking once.
  • Many callers behind one shared egress address, which share a single per-IP budget.
  • Protocol overhead: one assistant question costs several requests (initialize, tools/list, then the tool call).

How to fix it

  1. Honor the Retry-After header before retrying.
  2. Ask once and reuse the answer: readings only change once per probe cycle (10 minutes).
  3. For sustained or shared-egress use, switch to the keyed MCP endpoint with an API key, which has its own larger per-key budget.
  4. For a single service reading, the cacheable JSON endpoint at /api/v1/outages/<slug> is cheaper than an MCP round trip.

Related codes

  • RU-1006: Keyless MCP endpoint does not serve this tool
  • RU-6003: Public outage API rate limited

Still stuck?

Ask support and mention RU-6004: the code pins down the exact refusal path, so you skip the diagnostic back-and-forth.