Hanzo
Cloud MCPagents

post_v1_agents

CreateAgent defines an agent in the caller's org: a model, a system prompt (instructions) and a set of tool names. The name must be unique in the org and match ^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$.

CreateAgent defines an agent in the caller's org: a model, a system prompt (instructions) and a set of tool names. The name must be unique in the org and match ^[A-Za-z0-9][A-Za-z0-9._-]{0,63}$. An omitted model takes the deployment's configured default; a named one is checked against the gateway's served catalog, so a model this deployment never serves is refused here rather than failing at run time. A long-running agent must carry a 5-field cron schedule (the scheduler would otherwise never fire it) and counts against a per-org cap on scheduled agents.

Toolpost_v1_agents
Doorhttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments9
OperationPOST /v1/agents
Productagents

Arguments

FieldTypeRequiredDefaultDescription
computeRefstring
descriptionstring
executionModestring
instructionsstring
modelstring
namestring
schedulestring
serviceAccountIdstring
toolsstring[]

This tool's schema does not declare which fields are required, nor any default, nor any enumerated value set. The columns above are empty because the door publishes nothing there, not because the answer is "none" — where a field is constrained, the constraint is stated in that field's own description.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. Every declared argument is shown, because the door marks none of them required.

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",
         "arguments": {
           "computeRef": "<computeRef>",
           "description": "<description>",
           "executionMode": "<executionMode>",
           "instructions": "<instructions>",
           "model": "<model>",
           "name": "<name>",
           "schedule": "<schedule>",
           "serviceAccountId": "<serviceAccountId>",
           "tools": [
             "<tools>"
           ]
         }
       }
     }'

Values are placeholders derived from each field's declared type. 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
cloud_post_v1_agentsPOST /v1/agentsagentsCreateAgent defines an agent in the caller's org: a model, a system prompt (instructions)

The same capability over plain HTTP is in the agents API reference, on https://api.hanzo.ai.


All 834 tools · The door · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 834 tools captured 2026-08-01 (this build read the vendored copy; the door was unreachable).

How is this guide?

On this page