get_v1_agents_metrics
AgentMetrics serves the invocations-over-time histogram for the org's Agents dashboard.
AgentMetrics serves the invocations-over-time histogram for the org's Agents dashboard. Every point is a REAL count of recorded runs in that time bucket — one series line per agent that ran in the window. The Resource Usage rollup is all-null because this store meters no CPU/memory/storage/cost; the console renders those as "—" rather than a fabricated figure. No runs => empty series (an honest "not connected / no activity yet"), never a synthesized trend.
| Tool | get_v1_agents_metrics |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 1 |
| Operation | GET /v1/agents/metrics |
| Product | agents |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
range | string | — | — | — | Range is the window to bucket: 24H, 7D or 30D. Anything else reads as 30D. |
tools/list declares a type and a description for each field and nothing further. A — means neither the door nor that operation constrains the field.
Call it
A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Nothing above is required, so every declared argument is shown rather than a guess at which matter.
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_agents_metrics",
"arguments": {
"range": "<range>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. 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_get_v1_agents_metrics | GET /v1/agents/metrics | agents | AgentMetrics serves the invocations-over-time histogram for the org's Agents dashboard. |
The same capability over plain HTTP is in the agents API reference, on https://api.hanzo.ai.
All 833 tools · The door · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 833 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).
How is this guide?
get_v1_agents_builds_org_project
ReadBuild returns the readable build of one product: the agent session that produced it, turn by turn — the prompts, the reasoning, the commits each turn produced — plus the exact `git log` that…
get_v1_agents_ref
GetAgent returns one agent with its system prompt and its 20 most recent runs.