post_v1_agents_targets_id_runs_runId_report
ReportRoutedRun completes a claimed run: it delivers the terminal result to the run's durable owner, which is what lets that workflow finish.
ReportRoutedRun completes a claimed run: it delivers the terminal result to the run's durable owner, which is what lets that workflow finish. Scoped to (org, target, run) and claim-key-authenticated, so a machine can only ever report a run it legitimately holds. Idempotent — a report for an unknown or already-finished run answers delivered:false rather than failing, because the session's terminal state was already set by the machine's own stream.
| Tool | post_v1_agents_targets_id_runs_runId_report |
| Door | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 8 |
| Operation | POST /v1/agents/targets/{id}/runs/{runId}/report |
| Product | agents |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
branch | string | — | — | — | Branch, CommitSha and Diffstat describe what the run produced; Error is the failure when OK is false. Each is clamped, never rejected. |
changed | boolean | — | — | — | — |
commitSha | string | — | — | — | — |
diffstat | string | — | — | — | — |
error | string | — | — | — | — |
id | string | — | — | — | ID is the machine reporting, from the path. |
ok | boolean | — | — | — | OK is whether the run succeeded; Changed whether it produced any commit. |
runId | string | — | — | — | RunID is the routed run being completed, from the path. |
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": "post_v1_agents_targets_id_runs_runId_report",
"arguments": {
"branch": "<branch>",
"changed": false,
"commitSha": "<commitSha>",
"diffstat": "<diffstat>",
"error": "<error>",
"id": "<id>",
"ok": false,
"runId": "<runId>"
}
}
}'Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. changed and ok hold stand-ins that cannot be spelled that way — JSON gives a number, a boolean and a timestamp no placeholder form — so those values are this page's, not the API's. Neither the door nor the operation 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 |
|---|---|---|---|
post_v1_agents_targets_id_runs_runId_report | POST /v1/agents/targets/{id}/runs/{runId}/report | agents | Completes a claimed run: it delivers the terminal result to the run's durable owner,… |
The same capability over plain HTTP is in the agents 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?