shipapis
StarSubmit an APISubmit API

Lexigram vs RacingHub

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

APILexigramHEALTHY88RacingHubHEALTHY92
Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms807473
P95 · ms16723557
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?

Both are neck-and-neck — Lexigram and RacingHub each measure 99.02% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Lexigram or RacingHub?

RacingHub has the lower median latency in our checks — Lexigram responds in 807 ms versus RacingHub at 473 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

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.