Lists the effective published claims: what the leaderboard will use for each…

Lists the effective published claims: what the leaderboard will use for each (benchmark, model) after the seed, the import and any stored correction are…

GET /v1/benchmark/claims

Benchmark → · All API references → · Six flows, four surfaces →


Address	`https://api.hanzo.ai/v1/benchmark/claims`
Method	`GET`
Operation	`get_benchmark_claims`
Auth	`Authorization: Bearer $HANZO_API_KEY`

Lists the effective published claims: what the leaderboard will use for each (benchmark, model) after the seed, the import and any stored correction are layered. It answers the operator's question — what does this arena currently believe someone else reported, and did we ship that or fix it.

Effective values only. The history of a key lives in the append-only file and is not what this op is for; a list that returned every superseded row would make the common question the hard one.

Request

5 fields.

Field	In	Type	Required	Description
`Benchmark`	query	string	—	Benchmark filters to one benchmark id.
`Model`	query	string	—	Model filters to one model.
`Provider`	query	string	—	Provider filters to one lab or leaderboard — the way to read what a single source claims across every model it covers.
`Source`	query	string	—	Source filters to one citation, which is the finest grain there is: a source is what makes two claims about one model independent rather than a restatement of…
`Protocol`	query	string	—	Protocol filters by HOW a claim was scored, so provider cards can be read apart from third parties running their own harness.

Response

Status	Body	Meaning
`200`	claimsOut	ok

200 body — 11 fields.

Field	In	Type	Always	Description
`data`	body	ClaimRow[]	—	Data is one row per (benchmark, model, SOURCE) — every independent claim, not one per model.
`data[].at`	body	string (date-time)	—	At is when a stored row was recorded.
`data[].benchmark`	body	string	—	Benchmark is the canonical test id the claim is about, from /catalog.
`data[].by`	body	string	—	By is who recorded it, when the caller said.
`data[].model`	body	string	—	Model is the system the score is claimed for.
`data[].origin`	body	string	—	Origin is "seed" for a compiled row and "stored" for one written through this surface.
`data[].protocol`	body	string	—	Protocol records HOW it was scored — provider-reported, agentic, third-party-leaderboard — so a provider card is never read as a measurement.
`data[].provider`	body	string	—	Provider is who the claim belongs to — the lab or leaderboard whose number this is.
`data[].score`	body	number	—	Score is the reported aggregate, as a percentage.
`data[].source`	body	string	—	Source is the citation the row was read from.
`total`	body	integer	—	Total is how many rows Data holds.

Failure carries the platform error shape — see Errors.

Examples

hanzo benchmark claims get

import { Configuration, BenchmarkApi } from 'hanzoai';

const api = new BenchmarkApi(new Configuration({ accessToken: process.env.HANZO_API_KEY }));
const { data } = await api.getBenchmarkClaims();

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_claims()

cfg := cloud.NewConfiguration()
cfg.AddDefaultHeader("Authorization", "Bearer "+os.Getenv("HANZO_API_KEY"))
client := cloud.NewAPIClient(cfg)

resp, _, err := client.BenchmarkAPI.GetBenchmarkClaims(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_claims(&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).getBenchmarkClaims();

curl https://api.hanzo.ai/v1/benchmark/claims \
  -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"
         }
       }
     }'

Benchmark API · All Hanzo APIs · Interactive reference

Lists the effective published claims: what the leaderboard will use for each…

Request

Response

Examples

On this page