Hanzo OS
Agents
Workers the company keeps: a model, instructions, tools and a budget.
An agent is defined once in the org and run by name. Every run is recorded with its input, output, model and duration, and a session carries a cap it cannot exceed. Each subsystem’s operations are MCP tools, so an agent reaches the same surface a founder does.
API
Operations on api.hanzo.ai. One key reaches every layer.
| Method | Path | What it does |
|---|---|---|
POST | /v1/agent | Defines an agent in the org: a model, instructions and a set of tools. |
POST | /v1/agent/{ref}/run | Runs one of the org’s agents and returns the recorded run. |
GET | /v1/agent/{ref}/spend | Answers what one agent has spent, in micro-USD. |
POST | /v1/agent/sessions | Opens a live agent session in the org. |
POST | /v1/agent/sessions/{id}/budget | Sets, raises, or removes a session’s cap. |
POST | /v1/mcp | Every subsystem’s operations as MCP tools. |
Try it
curl https://api.hanzo.ai/v1/agent \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"name": "helper", "model": "enso-flash", "instructions": "be terse", "cap_micro_usd": 5000000, "period": "month"}'
curl https://api.hanzo.ai/v1/agent/helper/run \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{"input": "Summarise yesterday’s signups"}'