Hanzo
Cloud MCPbots

post_v1_bots_runId_stop

Stop terminates one of the caller org's own bot runs and reports its terminal state.

Stop terminates one of the caller org's own bot runs and reports its terminal state.

The own-key guard is the org: it is the caller's validated org, never theirs to choose, and the runtime resolves the run id UNDER it. A run belonging to another tenant is not among this org's runs, so it answers absent — the same 404 a nonexistent id gets, which is what keeps this from being an oracle.

Absence is honoured ONLY when the runtime answers it. A runtime that does not serve stop reports nothing about the run, and reporting "stopped" on that basis would be a stop that cannot fail — so it is a 502.

Toolpost_v1_bots_runId_stop
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments0
OperationPOST /v1/bots/{runId}/stop
Productbots

Arguments

The door declares no arguments for this tool.

POST /v1/bots/{runId}/stop requires runId, which tools/list does not declare on this tool. Where that value goes in a tools/call is not something the door publishes, so this page does not guess — the same capability over plain HTTP is fully specified in the API reference below.

Call it

A tools/call carries its arguments in one flat object. This tool declares none, so the object is empty — though the operation behind it requires runId, so this envelope is the shape of the call, not one that can name a resource.

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_bots_runId_stop",
         "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

OperationRouteProductSummary
post_v1_bots_runId_stopPOST /v1/bots/{runId}/stopbotsStop terminates one of the caller org's own bot runs and reports its terminal state.

The same capability over plain HTTP is in the bots 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?

On this page