Hanzo AI

Pref

Your own settings — theme, density, pinned nav — following you across every Hanzo app.

Also for this capability: API · CLI · SDKs

Your own settings — theme, density, pinned nav — following you across every Hanzo app.

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

Specification

Specification pending — no HIP in hanzoai/hips declares capability: pref 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
RESTpref at its own prefix2 operations
CLIhanzo pref …2 of 2
SDKPrefApi in every published client2 methods
MCPtool prefs on https://api.hanzo.ai/v1/mcp2 operations, 0 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/pref, operation get_pref:

hanzo pref get

Answers 200 with object — ok.

Endpoints

EndpointWhat it does
GET /v1/prefReturns the signed-in caller's OWN preference document — the theme, density and pinned nav that follow them across every Hanzo surface.
PATCH /v1/prefSave the preference keys your surface owns, leaving every other key alone

All Hanzo APIs · Interactive reference

How is this guide?