Hanzo AI

AI

ai: 294 operations.

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

ai: 294 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.

Toolai
Addresshttps://api.hanzo.ai/v1/mcp
Methodtools/call (JSON-RPC 2.0)
Arguments2, 1 required
OperationGET /v1/ai/mcp/tools · GET /v1/ai/account · GET /v1/ai/answer · GET /v1/ai/prometheus · GET /v1/ai/system · GET /v1/ai/version · POST /v1/ai/connections · POST /v1/ai/connections/{provider}
Productai

Arguments

FieldTypeRequiredDefaultValuesDescription
inputobjectarguments for the chosen op
opstringyesone of the operations below

op — what each one does:

  • create_chat — Implements the OpenAI-compatible chat completions API
  • create_chat_completion — Implements the OpenAI-compatible chat completions API
  • create_completion — Implements the OpenAI-compatible chat completions API
  • create_response — Implements POST /v1/responses.
  • create_message — Implements the Anthropic Messages API.
  • create_message_count_token — Implements POST /v1/messages/count_tokens.
  • create_embedding — Implements POST /v1/embeddings (OpenAI-compatible).
  • create_rerank — Implements POST /v1/rerank (Cohere/Jina-compatible).
  • list_models — Returns the list of available models from the routing table.
  • get_model_access — Returns the caller's own standing for a gated model: "granted", "requested", or empty when they have never asked.
  • list_model_providers — Public, secret-free list of the providers serving the models that GET /v1/models lists — the same source, projected.
  • access_model — Records the caller's waitlist request for a gated model and answers their new standing.

tools/list declares a type, a description, which fields are required and an enumerated value set for each field and nothing further, and every column above is MCP's own. This tool takes an operation name and that operation's arguments, so what the document constrains is what goes inside input, field by field, on the operation you name — ask describe for that. A means MCP does not constrain the field.

Call it

A tools/call carries every argument in one flat object — nothing binds to a path or a query string. This call carries exactly the arguments the operation requires, so it is the smallest one that can run.

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": "ai",
         "arguments": {
           "op": "list_models"
         }
       }
     }'

Values are the operation's own defaults and enumerated values where it declares them, and a <placeholder> where neither source declares one. tools/list needs no credential; tools/call does — called without one MCP 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

ai dispatches to 294 operations. 8 of them MCP names exactly as the document ids them, and those are below; for the rest MCP has its own verb, which describe resolves.

OperationRouteProductSummary
aiMCPToolsGET /v1/ai/mcp/toolsaiTools reports what THIS PROCESS's MCP server carries: how many tools its own registry…
get_ai_accountGET /v1/ai/accountaiAccount
get_ai_answerGET /v1/ai/answeraiAnswer
get_ai_prometheusGET /v1/ai/prometheusaiPrometheus
get_ai_systemGET /v1/ai/systemaiSystem
get_ai_versionGET /v1/ai/versionaiVersion
post_ai_connectionsPOST /v1/ai/connectionsaiConnects (or reconnects) a third-party AI account for the org by sealing the supplied key…
post_ai_connections_by_providerPOST /v1/ai/connections/{provider}aiDisconnects a third-party AI account: it deactivates the org's row so completion…

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


All 121 tools · MCP · API reference

Generated from tools/list on https://api.hanzo.ai/v1/mcp — 121 tools captured 2026-08-16.

How is this guide?