OpenChainBench

Docs

Every surface here is readable by a machine without a browser. One MCP server, eleven REST endpoints, the pages themselves as Markdown, and the data under CC BY 4.0. No key and no signup for any of it.

Section I

Where to start

  1. Using an AI assistant

    Point it at the MCP server and the benchmarks become a tool your model can call.

    Install instructions

  2. Writing code

    Eleven REST endpoints, no key and no signup, described by an OpenAPI 3.1 document.

    OpenAPI document

  3. Scraping or citing

    Ask any benchmark page for Markdown, or take a citation record in the format your tool imports.

    Citation formats

  4. Checking how a number was made

    Every figure is a query against a public Prometheus, and every bench links the harness that produced it.

    Methodology
Section II

MCP server

Streamable HTTP, no auth, 60 requests per minute per IP. The mcp transport is the only one served. Install it in Claude Desktop, Cursor or VS Code.

https://openchainbench.com/api/mcp/mcp
list_benchmarks
Flat index of every published benchmark with its current headline value, leader, category, unit and citation URL. The discovery call.
get_benchmark
One benchmark in full: every provider ranked by p50, a 24 h sparkline, the headline sentence, a paste-ready citation, the methodology bullets and the source-code URL. Takes chain and region where the bench declares them.
list_answers
Every answer page: a question in plain words, the sentence that answers it from live data, and the benchmark the number came from. For questions asked in words rather than by bench name.
query_prom
PromQL passthrough, scoped to the benchmark metric namespaces, for ranges and shapes the two tools above do not cover.

The server answers tools/list, which is the version of this list that cannot go stale.

Section III

REST API

No key, no signup. Responses are cached at the edge, so a client that polls faster than the data moves is served from cache rather than rate-limited.

/api/stat/{slug}

JSON

One benchmark: rankings, sparkline, and a quote ready to paste. Takes ?chain=, ?region= and ?tier= where the bench declares them.

/api/citable

JSON

Flat index of every citable benchmark with its current value.

/api/citable/{date}

JSON

The same index as it stood on one past day.

/api/cite/{slug}/{format}

bib · ris · apa · txt

One citation record with the right MIME type, so Zotero and EndNote import it directly.

/api/compare/{a}/{b}

JSON

Two providers head to head on every benchmark that measures both.

/api/capital

JSON

The /capital hub in one payload: chains, protocols and the valuation rows.

/api/freshness

JSON

Last resolved data timestamp. A cheap probe before a heavier call.

/api/llm-context

Markdown

Every benchmark, ranking and methodology note as one document.

/api/search/featured

JSON

Live leaders and trending benchmarks.

/api/sparkline/{slug}

SVG

The leader's 24 h series as a standalone image.

/api/og/{slug}

PNG

A 1200x630 card with the current value and sparkline.

The OpenAPI document is generated from the routes, so it is the one to trust if this table and it ever disagree.

Section IV

Pages as Markdown

Send Accept: text/markdown and these paths answer with the table instead of the DOM. An agent gets the numbers without parsing HTML.

curl -H 'Accept: text/markdown' https://openchainbench.com/benchmarks/ethereum-rpc
/benchmarks/{slug}/products/{slug}/perps/rwa/capital

Every other path answers HTML whatever the header asks for, /rpc and /chains/{slug} included.

Section V

Files written for agents

/llms.txt
The site in the llms.txt convention: what each section holds and when to cite it.
/llms-full.txt
The same, expanded, with the benchmark catalogue inline.
/api/llm-context
Every ranking and methodology note as one Markdown document.
Section VI

Citing a number

The data is CC BY 4.0. Attribution is OpenChainBench plus the benchmark page.

https://openchainbench.com/api/cite/ethereum-rpc/bib    # BibTeX
https://openchainbench.com/api/cite/ethereum-rpc/ris    # RIS, for Zotero and EndNote
https://openchainbench.com/api/cite/ethereum-rpc/apa    # APA, as plain text
https://openchainbench.com/api/cite/ethereum-rpc/txt    # one sentence with the value and date

Two DOIs, not interchangeable

10.5281/zenodo.20800311 is the concept DOI and follows the newest version, which is what a living reference wants. 10.5281/zenodo.20800312 is the current version, v1.0.1-dataset, and is the one to cite when a result has to stay reproducible.

A benchmark page moves

/api/citable is the index as it stands now. /api/citable/{date} is that index as it stood on a past day, which is what a paper should point at.

Section VII

Badges and embeds

An SVG badge with a live value, for a README or a status page. The badges catalog has one per benchmark and provider, and partners carries the embed terms.

https://openchainbench.com/api/badge/ethereum-rpc/drpc
Section VIII

Feeds and mirrors

Feeds

The same data elsewhere

If something here is wrong

A broken endpoint or a number that does not reproduce is worth a report, and both have a destination on the contact page. Adding a benchmark of your own is contribute.