Reference
Status badges
A live badge any provider can embed. It renders from the current measurement every time it is loaded, so it shows today’s figure or it shows nothing — which is the point. Free to use, no attribution required beyond the link the snippet already carries.
Build one
Provider
Metric
The composite score, coloured by band.
Treatment
The default. A README is as often dark as light.
Window
Longer windows read coarser rollups, so a 30-day percentile is a genuine merge rather than an average of averages.
my-app
Markdown
[](https://rpcnode.io/providers/nodereal)HTML
<a href="https://rpcnode.io/providers/nodereal"><img src="https://rpcnode.io/badge/provider/nodereal.svg?chain=bsc" alt="NodeReal on RPCNode.IO"></a>Image URL
https://rpcnode.io/badge/provider/nodereal.svg?chain=bscThe link points at the provider’s page, so a reader who clicks the badge lands on the measurements behind it.
The address
/badge/provider/{slug}.svg?chain={chain}&metric={metric}&style={style}&window={window}- slugA provider slug, with or without .svg
- The extension is accepted because some README renderers refuse to embed a URL that does not look like an image file.
- chainethereum · bsc · solana
- A provider serves different chains with different infrastructure and scores differently on each. Omitting this resolves to the first chain the provider is measured on, alphabetically, and the badge names it either way.
- metricscore · availability · latency · rank
- Defaults to
score. An unrecognised value falls back to it rather than erroring, so a badge in a README never breaks. - styledark · light · flat
- Defaults to
dark. A README is as often light as dark, and a near-black block punched into a white page is reason enough not to embed a badge at all.flatis the dark one without the gradient and the text shadow. - window1h · 6h · 24h · 7d · 30d
- Defaults to
24h. Longer windows read coarser rollups, so a 30-day percentile is a genuine merge rather than an average of averages.
What the badge will and will not do
It goes down with the score
The badge is rendered per request from the same ranking the site publishes. A provider whose availability falls will see the badge in its own README change colour, without anyone here doing anything. That is the property that makes it worth embedding — a badge that could be frozen at its best day would be a logo.
It says which chain and which window
Both are on the badge itself, not only in the URL. A figure without them can be quoted anywhere and defended everywhere, which is exactly what a measurement badge must not permit.
A rank always carries its cohort
“3 of 9”, never “3”. A bare position invites the reader to supply their own denominator, and they will pick a flattering one.
Too little data reads as too little data
A provider below the sample threshold gets a grey badge saying insufficient data, not a flattering number from a handful of calls. An unrecognised provider gets not measured and status 200, so the image renders and the reader can see what went wrong.
How every figure behind these badges is measured and scored is published in full. The methodology