Lexigram vs RacingHub

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedCC BY 4.0 (source data from the F1DB project)
Free tierFree tier — key may be requiredFree — no key required
Rate limitUnpublished100 req/window · 99 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lexigram vs RacingHub: common questions

Which is more reliable, Lexigram or RacingHub?

On our scheduled checks, RacingHub leads on measured uptime — Lexigram at —% versus RacingHub at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do Lexigram and RacingHub need an API key?

RacingHub needs no key, while Lexigram requires a free API key. If you want to start calling without signup, reach for RacingHub first.

Can I call Lexigram and RacingHub from the browser?

Only RacingHub is browser-friendly — it returns CORS headers over HTTPS. Lexigram needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Lexigram and RacingHub free for commercial use?

Lexigram has unclear commercial terms, and RacingHub has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.