Hanzo

Node

Package nodes is your machines: the ones you own, connected and ready to take a command.

Package nodes is your machines: the ones you own, connected and ready to take a command.

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

Specification

Specification pending — no HIP in hanzoai/hips declares capability: node 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
RESTnode at its own prefix4 operations
CLIno command reaches it yet — use HTTP or an SDK
SDKno published client declares one yet — regenerating the clients is what adds them
MCPno tool names it yet — use HTTP or an SDK

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/node, operation get_node:

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

Answers 200 with object — ok.

Endpoints

EndpointWhat it does
POST /v1/node/{id}/invokeAsk one of your connected machines to run a command, and get its answer back.
GET /v1/node/connectThe socket a bot node dials and holds open to become invokable.
POST /v1/node/peer/invokeReplica-to-replica forward of one invocation to the pod holding the node's socket.
GET /v1/nodeReturns the caller org's currently connected bot nodes: what each one calls itself, the platform it runs on, its agent version, when its socket was…

All Hanzo APIs · Interactive reference

How is this guide?

On this page