Take the data
Everything published here is CC BY 4.0. There is no API key and no registration. If you are building something with it, we would like to hear about it, but you do not need to ask.
The archive is Git
Accepted manifests are committed to the public repository every hour, one file per result, laid out by profile, version and GPU. That archive is canonical: the live database is an index rebuilt from it, not the other way round.
git clone https://github.com/pavel4ai/localmax.net.git ls localmax.net/results/llm-entry-base/0.1.0/rtx-4090/
Each file is the manifest exactly as it was submitted and signed. Nothing is edited after the fact; a correction is a new result with a finding attached, never a rewrite.
The read API
Public, cached at the edge, CORS-open for GET. Base URLhttps://api.localmax.net.
| Endpoint | Returns |
|---|---|
| GET /v1/profiles | Every profile with its pinned rules and result counts |
| GET /v1/profiles/:id | One profile in full, including workloads and gates |
| GET /v1/leaderboard/:id | Ranked results plus per-GPU distribution for one profile |
| GET /v1/results | All accepted results, filterable and paginated |
| GET /v1/results/:runId | One result with its full manifest, findings and percentile context |
| GET /v1/distribution/:id | Every ranked headline value for one profile, optionally by GPU |
| GET /v1/hardware | GPU registry with per-GPU result counts |
| GET /v1/hardware/:key | Per-profile aggregates for one GPU |
| GET /v1/compare?ids= | Two to four results side by side |
| GET /v1/stats | Site totals and the most recent results |
| GET /v1/evidence/:hash | One evidence artifact by content hash |
# Every ranked RTX 4090 result on the Entry BF16 profile curl 'https://api.localmax.net/v1/results?profile=llm-entry-base&gpu=rtx-4090&ranked=1' # The distribution behind a percentile figure curl 'https://api.localmax.net/v1/distribution/llm-entry-base?gpu=rtx-4090'
Schemas
The contracts are the source of truth for the whole project — the runner, the API and CI all validate against these same files.
- result.schema.json — one benchmark run
- profile.schema.json — an immutable benchmark definition
- api.schema.json — submission and read contracts
- common.schema.json — shared definitions
Attribution and caveats
Cite as: Data from LocalMax (localmax.net), CC BY 4.0.
Results are contributed by the public. A verification state describes the completeness and internal consistency of the evidence, not the honesty of the operator. Filter toverification=verified and ranked=1 for the strictest subset, and treat any single result as one sample rather than a specification.