shipapis
StarSubmit an APISubmit API

OpenF1 vs Squiggle

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

APIOpenF1NEW—SquiggleNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree & open (historical); real-time may require a free accountFree — no key
Rate limitRetry-After: 60sUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenF1 vs Squiggle: common questions

Which is more reliable, OpenF1 or Squiggle?

On our scheduled checks, Squiggle leads on measured uptime — OpenF1 at —% versus Squiggle 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 OpenF1 and Squiggle need an API key?

Neither needs a paid key — OpenF1 is callable with no signup, and Squiggle is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call OpenF1 and Squiggle from the browser?

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

Are OpenF1 and Squiggle free for commercial use?

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