shipapis
StarSubmit an APISubmit API

Lexigram vs OpenF1

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

APILexigramHEALTHY88OpenF1DYING57
Uptime · 30d
Uptime · 90d99.02%47.1%
Uptime · 30d98.3%41.7%
P50 · ms807747
P95 · ms16723525
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree & open (historical); real-time may require a free account
Rate limitUnpublishedRetry-After: 60s
In directory since2026-07-052026-07-05
operationalpartialdownno data

Lexigram vs OpenF1: common questions

Which is more reliable, Lexigram or OpenF1?

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

Which is faster, Lexigram or OpenF1?

OpenF1 has the lower median latency in our checks — Lexigram responds in 807 ms versus OpenF1 at 747 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 OpenF1 need an API key?

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

Can I call Lexigram and OpenF1 from the browser?

Only OpenF1 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 OpenF1 free for commercial use?

Lexigram has unclear commercial terms, and OpenF1 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.