Transport
transport: 8 operations.
Also for this capability: API · CLI · MCP · SDKs
transport: 8 operations. Name one in "op" and pass that operation's own arguments in "input". describe returns an operation's input schema.
| Tool | transport |
| Address | https://api.hanzo.ai/v1/mcp |
| Method | tools/call (JSON-RPC 2.0) |
| Arguments | 2, 1 required |
| Operation | GET /v1/transport/agent · GET /v1/transport/allowlist · GET /v1/transport/inbox · GET /v1/transport/pairing |
| Product | transport |
Arguments
| Field | Type | Required | Default | Values | Description |
|---|---|---|---|---|---|
input | object | — | — | — | arguments for the chosen op |
op | string | yes | — | — | — |
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": "transport",
"arguments": {
"op": "list_transports"
}
}
}'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
transport dispatches to 8 operations. 4 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.
| Operation | Route | Product | Summary |
|---|---|---|---|
get_transport_agent | GET /v1/transport/agent | transport | Returns which agent answers the caller org's transport: the default and every channel bound to another agent. |
get_transport_allowlist | GET /v1/transport/allowlist | transport | Returns the caller org's access policy for one transport: whether DMs are pairing-gated, allowlisted or open, whether group channels are open, allowlisted or disabled, the config-managed DM and group allow entries, the senders approved through PAIRING (read-only here), and the org's named access groups. |
get_transport_inbox | GET /v1/transport/inbox | transport | Returns the caller's own messages to the org's connected chat bots — those recorded on the caller's linked account — oldest first, in the portable envelope shape every transport normalises into. |
get_transport_pairing | GET /v1/transport/pairing | transport | Returns the pairing requests waiting for the caller org to approve — one per person who messaged a connected bot on a transport whose DM policy is "pairing" and who is not allowed yet. |
The same capability over plain HTTP is in the transport API reference, on https://api.hanzo.ai.
All 127 tools · MCP · API reference
Generated from tools/list on https://api.hanzo.ai/v1/mcp — 127 tools captured 2026-11-10.