get_v1_auto_status
Status reports whether the auto service is reachable — its own health endpoint as an honest lens for "is the automation plane up".
Status reports whether the auto service is reachable — its own health endpoint as an honest lens for "is the automation plane up".
| Tool | get_v1_auto_status |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 0 |
| Operation | GET /v1/auto/status |
| Product | auto |
Arguments
This tool declares no arguments. Call it with an empty arguments object.
Call it
A tools/call carries its arguments in one flat object. This tool declares none, so the object is empty.
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": "get_v1_auto_status",
"arguments": {}
}
}'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
| Operation | Route | Product | Summary |
|---|---|---|---|
get_v1_auto_status | GET /v1/auto/status | auto | Status reports whether the auto service is reachable — its own health endpoint as an… |
The same capability over plain HTTP is in the auto API reference, on https://api.hanzo.ai.
All 755 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01, of which 755 are documented here (the operator surface is not published) (this build read the vendored copy; the door was unreachable).
How is this guide?
get_v1_auto_runs_run
Run reads one run record: status, input, output (each executed node's result keyed by node id once completed), error detail if it failed, and timestamps.
patch_v1_auto_flows_flow
FlowUpdate patches one of the caller's flows: the name, the graph, or both — only the stated fields move.