Hanzo AI

Tool

Everything your org can call, in one list: connector actions, functions, agents, skills and your own MCP servers.

Also for this capability: API · CLI · MCP · SDKs

Everything your org can call, in one list: connector actions, functions, agents, skills and your own MCP servers.

Base URLhttps://api.hanzo.ai
Operations19
AuthAuthorization: Bearer $HANZO_API_KEY

Specification

Specification pending — no HIP in hanzoai/hips declares capability: tool yet. What this capability serves is below, from the API document; what it is — the store it owns, how it meters, what it publishes — is written as a HIP under HIP-0139.

Four surfaces

SurfaceReaches this capability asCoverage
RESTtool at its own prefix19 operations
CLIhanzo tool …19 of 19
SDKno published client declares one yet — regenerating the clients is what adds them
MCPtool tools on https://api.hanzo.ai/v1/mcp19 operations, 1 under the document's own id — ask describe for the rest

Quickstart

export HANZO_API_KEY=sk-...   # console.hanzo.ai → API keys

Then the first call — a read that needs nothing but the key. GET /v1/tool, operation get_tool:

hanzo tool get

Answers 200 with object — ok.

Endpoints

EndpointWhat it does
GET /v1/tool/activationReports which tools are switched on for the caller's org and project.
PUT /v1/tool/activationSwitches tools on and off for the caller's org and project, and answers with the resulting activated set.
POST /v1/tool/callRuns one of the caller's activated tools and answers with its output.
GET /v1/tool/catalog/{id}Returns one catalog entry in full: the publisher's description, its repository and site, every package form with the runtime that launches it, and…
PATCH /v1/tool/catalog/{id}Sets what WE say about one catalog entry — hidden, featured, official, logo — and answers with the stored listing.
POST /v1/tool/catalog/syncPulls the public MCP registry into our canonical copy and reports what changed.
GET /v1/tool/catalogLists the MCP servers the public registries publish, as we hold them: our canonical copy of registry.modelcontextprotocol.io, plus what we decided…
DELETE /v1/tool/mcp/servers/{id}Deregisters one of the caller org's external MCP servers, so its tools leave the registry.
GET /v1/tool/mcp/serversLists the external MCP servers the caller's org has registered.
POST /v1/tool/mcp/serversGives the caller's org one more external MCP server, so its tools join the org's tool plane and the fleet's MCP server.
DELETE /v1/tool/plugins/authored/{id}Removes one of the caller org's built plugins, so the runtime can no longer load it.
GET /v1/tool/plugins/authoredLists the plugins the caller's org BUILT, newest first, each with the TypeScript as authored.
POST /v1/tool/plugins/buildBuilds and stores one plugin for the caller's org.
GET /v1/tool/pluginsReports what this deployment actually mounted: every subsystem the composition root declared and whether it is switched on.
DELETE /v1/tool/skills/{id}Removes one of the caller org's authored skills.
GET /v1/tool/skills/authoredLists the caller org's OWN skills with their SKILL.md bodies.
GET /v1/tool/skillsLists the skills the caller's org can reach — the brand's embedded catalogue plus the org's own authored ones — with each one's activation flag.
POST /v1/tool/skillsAdds or revises one of the caller org's own skills, and answers 201 with the stored record.
GET /v1/toolLists every tool the caller's org and project can reach, from every source, each flagged with whether it is activated.

All Hanzo APIs · Interactive reference

How is this guide?