Pref
Package prefs is your own settings — theme, density, pinned nav — following you across every Hanzo app.
Package prefs is your own settings — theme, density, pinned nav — following you across every Hanzo app.
| Base URL | https://api.hanzo.ai |
| Operations | 2 |
| Auth | Authorization: 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
| Surface | Reaches this capability as | Coverage |
|---|---|---|
| REST | pref at its own prefix | 2 operations |
| CLI | hanzo prefs … | 2 of 2 |
| SDK | — | no published client declares one yet — regenerating the clients is what adds them |
| MCP | tool prefs on https://api.hanzo.ai/v1/mcp | 2 operations, 0 under the document's own id — ask describe for the rest |
Quickstart
export HANZO_API_KEY=sk-... # console.hanzo.ai → API keysThen the first call — a read that needs nothing but the key. GET /v1/pref, operation get_pref:
hanzo prefs getimport { Configuration, PrefApi } from 'hanzoai';
const api = new PrefApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getPref();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import PrefApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = PrefApi(client).get_pref()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.PrefAPI.GetPref(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, pref_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = pref_api::get_pref(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.PrefApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new PrefApi(client).getPref();The method above is the one at the current release of the document. [email protected] (npm) and [email protected] (PyPI) were generated from an earlier release, where this operation carried a different id, so it spells the method differently — regenerating the clients is what makes the two agree. SDKs →
curl https://api.hanzo.ai/v1/pref \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches pref through the prefs tool, which names its 2 operations with its own verbs — this one among them, under a name only the door declares. describe explains any of them:
curl -X POST https://api.hanzo.ai/v1/mcp \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "describe",
"arguments": {
"op": "list_prefs"
}
}
}'Answers 200 with object — ok.
Endpoints
| Endpoint | What it does |
|---|---|
GET /v1/pref | Returns the signed-in caller's OWN preference document — the theme, density and pinned nav that follow them across every Hanzo surface. |
PATCH /v1/pref | Save the preference keys your surface owns, leaving every other key alone |
How is this guide?