# Documentation Page **Page:** kit/agent/bot-urls/status/reference [Download Raw Markdown](./kit/agent/bot-urls/status/reference.md) --- # Bot URL status reference Lookup tables for [Bot URL status, access log and lifecycle](/kit/agent/bot-urls/status/). ## What callers see For supported Bot operations that require a key, Off, Frozen, Detached and suspended URLs return `key_invalid` without a valid key and `bot_disabled` with one. Keyless `GET /` and `GET /SKILL.md` remain available. CORS preflights on supported paths are also keyless: they succeed when browser access is enabled, or return `cors_disabled`, unless Bot URLs are switched off on the server or everywhere. The following availability errors can also be returned without a key: | Case | Every request gets | |---|---| | Bot URLs switched off on the computer's server (`host_off`) or everywhere (`global_off`) | `bot_disabled` | | A label that does not exist, and a detached or deleted URL once its address is gone | `bot_not_found` | ## Access log lines Each line holds metadata only: | Field | Value | |---|---| | `tsMs`, `durationMs`, `status`, `bytesSent` | When, how long, the HTTP status and the size of the answer | | `method`, `url` | The method and the path, such as `POST /v1/chat/completions`. Never the query string, so never a `?key=`. | | `clientIp` | The caller's IPv4 address | | `traceId` | The request id the caller received in `X-Request-Id` | | `serviceName` | `bots` | | `data.bot_exposure` | The id of the Bot URL that was called, `bu_…` | | `data.bot_label` | When present, the label that was called | | `data.bot_caller`, `data.bot_caller_name` | The key's id and name, or `null` when no valid key was sent | | `data.bot_door` | `openai`, `anthropic`, `mcp`, `manual` (`GET /`), `skill` (`GET /SKILL.md`), `preflight` (a browser `OPTIONS`) or `other` | | `data.bot_result` | `ok`, `client_closed` (the caller left before the answer was complete), `request_timeout` (the request body paused for more than 30 seconds and the connection was closed with no answer), or the [error code](/kit/agent/bot-urls/errors/) the caller received | | `data.bot_limit` | On a limit refusal: which limit, `{scope, kind, max, retry_at}` | ## Log gaps and retention | What | Detail | |---|---| | Refusals that leave no line | A plain `http://` request, a request over IPv6, a malformed address, a call to the server the URL was moved away from, a call refused because a Hoody service was unavailable before the URL could be identified | | Lost lines | A line can occasionally be lost on its way | | Logged nowhere | Calls to a label that does not exist, and calls to a detached or deleted URL | | Retention | The proxy logs' retention, by default 7 days, 50,000 entries or 100 MB per computer, whichever comes first | ## Log queries | Rule | Detail | |---|---| | Numeric filters | Send each of `afterId`, `last`, `limit`, `offset`, `sinceMs`, `untilMs` once, as a whole number without a sign or fraction | | Minimums | `last` and `limit` at least 1, the others at least 0 | | A repeated or invalid value | `400 INVALID_QUERY_PARAMETER`; `error` names the argument. An empty value, such as `?last=`, counts as not sent | | `last` | Returns at most 1000 entries, even when you ask for more | | A password group protects the logs | Send its username and password with HTTP Basic auth; without valid credentials the answer is `401` | | Caching | Log results and the `400`, `429` and `503` responses carry `Cache-Control: private, no-store` | The other filters and the live stream are on [Proxy Logs](/api/proxy-logs/). ## Lifecycle | What happens | The URL | Callers get | |---|---|---| | You turn the URL off, or back on | Off. Turning off preserves any stronger status. Changing the switch from off to on is refused with `409 BOT_URL_FROZEN` while frozen; otherwise the status is worked out again, and a suspension can keep it Off | `bot_disabled`, or answers when the URL is Active | | You change CORS or limits | The status does not change | The new settings, within about 11 seconds after they are applied | | You re-point it to another computer | Refused with `409 BOT_URL_FROZEN` while frozen. Otherwise attached to the new computer; your on/off switch and any suspension still apply | Answers from the new Bot when the URL is Active | | The computer is deleted, or the server it was on ends or is no longer yours | Frozen if it already was; otherwise Detached. Label and keys kept | `bot_disabled` for a caller with a valid key, then `bot_not_found` | | You re-point a detached URL | Refused while frozen; otherwise attached again, with status worked out from your on/off switch and any suspension | Answers when the URL is Active | | You delete the URL | Gone; the label stays taken forever | `bot_not_found` | | The project, your account or the server is deleted | Gone; the label stays taken forever | `bot_not_found` | | Hoody freezes or unfreezes it | Frozen; after unfreezing, whatever its current settings give | `bot_disabled`, or answers again if nothing else turned it off | | A suspension starts or ends | Frozen and Detached keep their status; otherwise Off (`suspended`). After it ends, whatever its current settings give | `bot_disabled`, or answers again if nothing else turned it off | | You press panic | Off, unless Frozen, Detached or a suspension applies; every key revoked | `key_invalid` | | The Bot is deleted or recreated in the agent | Status unchanged | `bot_disabled` for requests forwarded to the Bot with a valid key, until you re-point; `GET /v1/key` still returns the key's name and holder note while the URL is Active | ## Moves that wait While a former server has not stopped serving the old address, the move remains blocked. `propagation.state` can be `pending` or `failed`. An entry in `propagation.deny_targets` with `blocking: true` identifies a blocking former server when its details are available. The move can complete after that server stops serving the address or Hoody removes it from service.