Hanzo

Appearance

Package account is your own account: API keys you mint and revoke, and org onboarding.

Package account is your own account: API keys you mint and revoke, and org onboarding.

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

Quickstart

export HANZO_API_KEY=hk-...   # console.hanzo.ai → API keys

Then the first call — a read that needs nothing but the key. GET /v1/appearance, operation get_appearance:

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.

appearance

GET /v1/appearance

Returns the signed-in caller's own appearance preference — text size, density and accent — read from their IAM account so it is the same on every device and every Hanzo surface. An unset preference is an empty object.

A transient IAM read failure reports the empty preference rather than a 5xx, so a surface applies its published default and never error-toasts on load — the same fail-soft the key read uses.

POST /v1/appearance

Stores the caller's appearance preference on their IAM account, preserving every other field of the row. The accent is validated as a real colour token before it is stored; an unset or invalid axis is dropped rather than stored.

Request bodyapplication/json (required)

FieldTypeRequiredDescription
accentstringAccent is the one hue — a CSS colour token (a hex, or a bounded functional colour like rgb()/oklch()).
densitystringDensity is the spacing step: "compact", "default" or "comfortable".
typenumberType is the text-size multiplier, clamped to the ramp window [0.85, 1.4].

All Hanzo APIs · Interactive reference

How is this guide?

On this page