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
| Address | https://api.hanzo.ai/v1/bot/runs |
| Method | POST |
| Operation | post_bot_runs |
| Auth | Authorization: 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
| Status | Body | Meaning |
|---|---|---|
501 | — | not implemented |
Failure carries the platform error shape — see Errors.
Examples
hanzo bot runs createimport { Configuration, BotApi } from 'hanzoai';
const api = new BotApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postBotRuns();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import BotApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = BotApi(client).post_bot_runs()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.BotAPI.PostBotRuns(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, bot_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = bot_api::post_bot_runs(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.BotApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new BotApi(client).postBotRuns();curl -X POST https://api.hanzo.ai/v1/bot/runs \
-H "Authorization: Bearer $HANZO_API_KEY"MCP reaches bot through the bot tool, which names its 4 operations with its own verbs — this one among them, under a name only MCP declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "get_bot_connect"
}
}
}'How is this guide?