adminCompute
Rolls the fleet's compute usage up to one row per (org, app, project, kind): how many distinct machines ran in the window, how many are still active, what they billed, and when each group last emitted
Rolls the fleet's compute usage up to one row per (org, app, project, kind): how many distinct machines ran in the window, how many are still active, what they billed, and when each group last emitted an event. The console folds these into its org → app → project tree.
A machine counts as ACTIVE when its LATEST lifecycle event is not a terminal one (stop/destroy/terminate/delete/off/shutdown/expire and their past tenses) — the same fold the console applies, done in the warehouse so the count is over every machine and not just the page.
Honest-empty when the warehouse is not connected or hanzo.compute_usage is not provisioned yet: an empty list, never a fabricated fleet.
| Tool | adminCompute |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 3 |
| Operation | GET /v1/admin/compute |
| Product | cloud |
Arguments
| Field | Type | Required | Default | Description |
|---|---|---|---|---|
kind | string | — | — | Kind narrows to one workload class (bot | machine | cluster | nodepool | container | function | …). An OPEN spectrum matched as a plain string, lowercased to the warehouse's convention; empty means every kind. |
org | string | — | — | Org narrows to one tenant. Empty means every tenant — this board is cross-tenant by nature. |
range | string | — | — | Range is the lower time bound: 24h, 7d or 30d. Anything else reads as 30d. |
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": "adminCompute",
"arguments": {
"kind": "<kind>",
"org": "<org>",
"range": "<range>"
}
}
}'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
| Operation | Route | Product | Summary |
|---|---|---|---|
cloud_adminCompute | GET /v1/admin/compute | cloud | Rolls the fleet's compute usage up to one row per (org, app, project, kind): how many dist |
The same capability over plain HTTP is in the cloud 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?