Hanzo

Network

Package network mounts the Hanzo Cloud NETWORKING surface: the tenant's Hanzo Zero Trust footprint — the overlay network, its routers and its services — served as clean, org-scoped REST off the…

Package network mounts the Hanzo Cloud NETWORKING surface: the tenant's Hanzo Zero Trust footprint — the overlay network, its routers and its services — served as clean, org-scoped REST off the unified cloud binary and fronting the Hanzo Zero Trust controller (hanzoai/zt, an OpenZiti-based fabric).

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

Specification

Specification pending — no HIP in hanzoai/hips declares capability: network 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
RESTnetwork at its own prefix4 operations
CLIhanzo networks …3 of 4 — the CLI pins the document on its own clock
SDKno published client declares one yet — regenerating the clients is what adds them
MCPtool zt on https://api.hanzo.ai/v1/mcp4 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/network, operation get_network:

hanzo networks list

Answers 200 with object — ok.

Endpoints

EndpointWhat it does
GET /v1/network/{id}Returns one overlay network by id, scoped to the caller's org.
GET /v1/network/routersReturns the Zero Trust routers the caller's org owns.
GET /v1/network/servicesReturns the Zero Trust edge services the caller's org owns.
GET /v1/networkReturns the caller's org overlay network on the Zero Trust fabric.

All Hanzo APIs · Interactive reference

How is this guide?

On this page