Skip to content

Beta: these docs are still being updated. The next full update is on 18 November at 8 PM UTC. Docs in beta. Full update 18 Nov, 8 PM UTC.

Hoody.com

A Bot URL gives one of your Bots an address of its own on the internet, such as https://amber-falcon-river-k7m2q.hoody.bot. Anyone who holds a key you made for it can talk to the Bot from a browser, a coding agent, an OpenAI client, an Anthropic client, an MCP client or plain curl. Nothing else about the computer is reachable through it.

A Bot is a long-running assistant inside the Hoody Agent. It talks with you and hands real work to agents it starts on your computers. Its own computer URL is meant for you. A Bot URL is the address you give to other people and to the apps they use.

https://www.hoody.bot is a short page about Bot URLs, not a Bot. Short names such as www can never be labels.

PartWhat it is
LabelThe first part of the address: <label>.hoody.bot. Generated for you by default, or chosen by you. It belongs to your URL forever and is never given to anyone else.
KeysNamed secrets, one per person or app (for example alice or zapier). Each key can be paused, limited to IPv4 addresses, given an expiry date, or revoked on its own.
DoorsThe ways in: the OpenAI doors (/v1/chat/completions, /v1/responses, /v1/models), the Anthropic door (/v1/messages) and the MCP server (/mcp). Every door reaches the same Bot.
StatusActive, Off (disabled in the API), Detached or Frozen, shown in the Hub with the reason.
Access logBest-effort metadata lines in the computer’s existing proxy logs for the calls that reach it, refused calls included: who called, from where and with what result. It never holds what was said.

You create and manage Bot URLs in the Hub or through the Hoody API. In the agent, the Bot URLs tab creates a Bot’s URL, creates and revokes its keys and deletes the URL, and a Bot’s Connect window links to it; see From the agent.

A Bot URL is for people and apps you already trust: a teammate, a client, your own automation. It is not a way to publish a Bot to strangers.

The Bot sees who is talking. Each message reaches it with the key’s name, for example alice, so it can tell callers apart. The caller’s IP address is shown to you, the owner, in the access log, and never to other key holders.

You do. Every call runs on your Bot with your models, and uses your Hoody AI limits and credit or your provider keys: the Bot’s own replies, the work of the agents it starts, speech, and the small side requests some apps send (a conversation title, for example). Callers pay nothing and need no Hoody account.

Request limits bound what callers can spend: a per-minute limit that applies to each key, one for the whole Bot, and caps on simultaneous calls. They count requests, not money, and reserve nothing for any one caller. See Errors and limits.

One model

The model list holds one model, and its id is the label. A caller may send any model name; the Bot answers either way.

Your Bot's answers

Replies, the Bot’s notes on its work, and the questions its agents ask. Internal identifiers such as session and computer ids are replaced in what the Bot writes, and so is anything shaped like one, such as a UUID, which shows as [hidden]. What people type is shown as written.

A chat page and a manual

Opened in a browser, the URL shows a chat page that asks for a key. Tools and AI agents get a short text manual at GET / and GET /SKILL.md instead. Neither names your Bot, and fetching them never wakes your computer.

Clear errors

Every refusal carries a fixed error code in the door’s own error format, plus a request id that matches your access log.

  1. In the Hub, open Bots, select the Bot and open Link and keys.
  2. Choose Give it a link. Keep the suggested name or enter one under Name in the address, then choose Create link.
  3. Choose New key, enter a Name (the person or app that will use it), then choose Make key.
  4. Copy the secret under Copy the key “name” now, then choose I’ve stored it. The secret is shown once.
  5. Check the key. Set HOODY_BOT_URL to the URL you created in step 2, then paste the key when read waits; it is not shown and stays out of your shell history:
Terminal window
read -rs HOODY_BOT_KEY && export HOODY_BOT_KEY
printf 'Authorization: Bearer %s\n' "$HOODY_BOT_KEY" |
curl -sS "${HOODY_BOT_URL%/}/v1/models" --header @-

A list with one model, whose id is your label, means the URL works. Then hand the URL and the key to the caller. They can open the URL in a browser, or follow Call a Bot URL.