Are the router blends available to compose from — a named set of model arms,…
Are the router blends available to compose from — a named set of model arms, the rank they escalate through and the panel width that bounds fan-out — each…
GET /v1/benchmark/presets
| Address | https://api.hanzo.ai/v1/benchmark/presets |
| Method | GET |
| Operation | get_benchmark_presets |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Are the router blends available to compose from — a named set of model arms, the rank they escalate through and the panel width that bounds fan-out — each served by the model layer as enso-<name>.
Today it answers exactly one row, the reference blend: a worked example written in models we name, published as an example of the FORM. It is deliberately not the composition of a Hanzo-served tier — the tier name exists to abstract that — so fork it and swap arms by what the leaderboard measures on your own tasks rather than reading it as a disclosure.
Request
GET /v1/benchmark/presets takes no parameters and no body — the credential is the whole request.
Response
| Status | Body | Meaning |
|---|---|---|
200 | presetList | ok |
200 body — 7 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
data | body | Preset[] | — | Data is the blends available to compose from. |
data[].arms | body | string[] | — | the blend — model ids from the arena |
data[].name | body | string | — | served as enso-<name> |
data[].note | body | string | — | why this blend (audit) |
data[].owner | body | string | — | scoping org (never cross-tenant) |
data[].panel | body | integer | — | fan-out width (>=1) |
data[].rank | body | string[] | — | escalation order over arms |
Failure carries the platform error shape — see Errors.
Examples
hanzo benchmark presets getimport { Configuration, BenchmarkApi } from 'hanzoai';
const api = new BenchmarkApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getBenchmarkPresets();from hanzoai.cloud import ApiClient, Configuration
from hanzoai.cloud.api import BenchmarkApi
client = ApiClient(Configuration(access_token=os.environ["HANZO_API_KEY"]))
result = BenchmarkApi(client).get_benchmark_presets()cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.BenchmarkAPI.GetBenchmarkPresets(context.Background()).Execute()
if err != nil {
return err
}use hanzo_cloud::apis::{configuration::Configuration, benchmark_api};
let mut cfg = Configuration::new();
cfg.bearer_access_token = std::env::var("HANZO_API_KEY").ok();
let result = benchmark_api::get_benchmark_presets(&cfg, Default::default()).await?;import ai.hanzo.cloud.ApiClient;
import ai.hanzo.cloud.api.BenchmarkApi;
ApiClient client = new ApiClient();
client.setRequestInterceptor(b -> b.header("Authorization", "Bearer " + System.getenv("HANZO_API_KEY")));
var result = new BenchmarkApi(client).getBenchmarkPresets();curl https://api.hanzo.ai/v1/benchmark/presets \
-H "Authorization: Bearer $HANZO_API_KEY"The door reaches benchmark through the benchmark tool, which names its 6 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": "get_benchmark_catalog"
}
}
}'How is this guide?