Skip to content
#0341
ContainersAgent

Each department's automation sees only its own realm

Finance runs an agent that reconciles invoices. Helpdesk runs one that triages tickets. Both call the Hoody API. Both have tokens. IT's fear is the obvious one: the wrong agent, a confused prompt, a DELETE aimed at the wrong container.

So each department gets a realm. Finance's containers carry the finance realm ID; helpdesk's carry theirs. Each agent's token is realm-restricted with allow_no_realm: false, and it talks to https://{realmId}.api.hoody.com. On that host a container list returns only that realm's containers. Another realm's containers can't be discovered, enumerated, or addressed, not by mistake and not on purpose. The helpdesk agent does not know finance exists.

Forty departments, forty realms, one account, one bill. No network segmentation project, no per-team Hoody accounts, no shared root token anyone has to rotate.

Blast radius is a subdomain.