getBot
Returns one of the caller org's bot machines with its agent binding.
Returns one of the caller org's bot machines with its agent binding.
A machine counts as a Bot if it carries the hanzo-kind:bot tag OR has an agent binding — either signal is authoritative, so a bot resolves even before its cloud-init has stamped every tag. A machine that is neither is 404: this route answers for bots, not for machines.
| Tool | getBot |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 1 |
| Operation | GET /v1/bots/{id} · GET /v1/compute/bots/{id} |
| Product | visor |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
id | string | — | — | ID is the bot machine's id — the same id the machines surface addresses it by. Scoped to the caller's org upstream, so another tenant's id is 404. |
This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "getBot",
"arguments": {
"id": "<id>"
}
}
}'Values are placeholders derived from each field's declared type. tools/list needs no credential; tools/call does — called without one the door answers HTTP 200 with a JSON-RPC result whose isError is set and whose text says what was missing. How to get a key →
The operation behind it
The document uses this name for 2 operations and the door does not say which it dispatches to. Both are listed.
| Operation | Route | Product | Summary |
|---|---|---|---|
visor_getBot | GET /v1/bots/{id} | visor | Get one bot by id |
cloud_getBot | GET /v1/compute/bots/{id} | compute | Returns one of the caller org's bot machines with its agent binding. |
The same capability over plain HTTP is in the visor API reference, on https://api.hanzo.ai.
All 834 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?