Hanzo AI
OpenapiBot

Create runs

Answers 501 to every call: launching a bot run is not implemented. The bot runtime exposes no launch operation, so nothing here can start a sandbox.

POST /v1/bot/runs

Addresshttps://api.hanzo.ai/v1/bot/runs
MethodPOST
Operationpost_bot_runs
AuthAuthorization: Bearer $HANZO_API_KEY

Answers 501 to every call: launching a bot run is not implemented.

The bot runtime exposes no launch operation, so nothing here can start a sandbox. This address is published rather than dropped because it is the collection every run is created in: GET lists them, POST would launch one.

The refusal is total and takes no input. No run id is minted, no session URL is handed back, and no per-run fee is charged. That is the point: the earlier version minted an id the runtime had never heard of, pointed it at a VNC node that did not exist, and took real money for it. 501 is the truth, and the truth is cheaper than a plausible lie.

Listing and stopping runs are live and org-scoped. Only the launch is missing, and it returns in the same change that can prove a bot boots — a runtime-side launch operation first (TS, cross-repo), with the entitlement gate and the meter beside it.

Request

The document declares no body for POST /v1/bot/runs. The handler is typed in cloud but its shape is not yet emitted, so the fields are not listed here — ask MCP's describe for post_bot_runs, which answers from the running route.

Response

StatusBodyMeaning
501not implemented

Failure carries the platform error shape — see Errors.

Examples

hanzo bot runs create

Bot API · All Hanzo APIs · Interactive reference

How is this guide?

On this page