Validates a router blend — its name, its arms, the rank they escalate through…
Validates a router blend — its name, its arms, the rank they escalate through and the panel fan-out width — and answers 202 with the preset and the…
POST /v1/benchmark/presets
| Address | https://api.hanzo.ai/v1/benchmark/presets |
| Method | POST |
| Operation | post_benchmark_presets |
| Auth | Authorization: Bearer $HANZO_API_KEY |
Validates a router blend — its name, its arms, the rank they escalate through and the panel fan-out width — and answers 202 with the preset and the enso-<name> it would be served as.
It VALIDATES AND ECHOES: the definition is not persisted yet, so a preset accepted here is not one the model layer will resolve. Treat the response as a check on the blend, not a promise to serve it.
Defaults fill the shape rather than refusing it: an omitted rank becomes the arms in declared order and a panel below 1 becomes 1. The one real invariant is that rank may only name arms the blend declares — the same rule the model catalog enforces — and a rank naming anything else is a 422 listing exactly which entries were undeclared. A blend with no name or no arms is a 400.
Request
6 fields, body application/json (required).
| Field | In | Type | Required | Description |
|---|---|---|---|---|
arms | body | string[] | — | the blend — model ids from the arena |
name | body | string | — | served as enso-<name> |
note | body | string | — | why this blend (audit) |
owner | body | string | — | scoping org (never cross-tenant) |
panel | body | integer | — | fan-out width (>=1) |
rank | body | string[] | — | escalation order over arms |
Response
| Status | Body | Meaning |
|---|---|---|
202 | presetAccepted | accepted |
202 body — 10 fields.
| Field | In | Type | Always | Description |
|---|---|---|---|---|
note | body | string | — | Note explains what acceptance does and does not promise. |
preset | body | Preset | — | |
preset.arms | body | string[] | — | the blend — model ids from the arena |
preset.name | body | string | — | served as enso-<name> |
preset.note | body | string | — | why this blend (audit) |
preset.owner | body | string | — | scoping org (never cross-tenant) |
preset.panel | body | integer | — | fan-out width (>=1) |
preset.rank | body | string[] | — | escalation order over arms |
served_as | body | string | — | ServedAs is the model id the serving layer would resolve this blend under. |
status | body | string | — | Status is "accepted": the blend is well-formed, not that it is now served. |
Failure carries the platform error shape — see Errors.
Examples
hanzo benchmark presets createimport { Configuration, BenchmarkApi } from 'hanzoai';
const api = new BenchmarkApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.postBenchmarkPresets({ arms: ["<arms>"], name: "<name>" });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).post_benchmark_presets(arms=["<arms>"], name="<name>")cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)
resp, _, err := client.BenchmarkAPI.PostBenchmarkPresets(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::post_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).postBenchmarkPresets();curl -X POST https://api.hanzo.ai/v1/benchmark/presets \
-H "Authorization: Bearer $HANZO_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"arms": [
"<arms>"
],
"name": "<name>"
}'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?