Hanzo
OpenapiOpenapi

The agent door: every subsystem's operations as MCP tools

Model Context Protocol over JSON-RPC 2.0 — one POST per message, stateless, protocol revision 2026-07-28.

POST /v1/mcp

Addresshttps://api.hanzo.ai/v1/mcp
MethodPOST
Operationpost_mcp
AuthAuthorization: Bearer $HANZO_API_KEY

Model Context Protocol over JSON-RPC 2.0 — one POST per message, stateless, protocol revision 2026-07-28. tools/list answers without a credential with one tool per subsystem (its operations in the "op" enum) plus "describe", which returns one operation's input schema. tools/call names a subsystem tool and carries {"op": <operation>, "input": <its arguments>}; it takes the same bearer the REST API does, and a call that carries none is answered 401 with a WWW-Authenticate header naming the resource metadata at /.well-known/oauth-protected-resource, which names the authorization server to sign in at. The tool surface is the public contract: the operator's admin product is not offered, and a name that would disclose a secret or mutate an identity is withheld — the list says how many, under _meta.

Request

5 fields, body application/json.

FieldInTypeRequiredDescription
idbodyany
jsonrpcbodystring
methodbodystring
paramsbodyobject
params.*bodyany

Response

StatusBodyMeaning
2XXMCPResponseSuccess

2XX body — 8 fields.

FieldInTypeAlwaysDescription
errorbodyMCPError
error.codebodyinteger
error.databodyany
error.messagebodystring
idbodyany
jsonrpcbodystring
resultbodyobject
result.*bodyany

Failure carries the platform error shape — see Errors.

Examples

hanzo has no subcommand for this operation — the CLI serves only what cloud's live route table confirms. Use HTTP or an SDK.


Openapi API · All Hanzo APIs · Interactive reference

How is this guide?

On this page