RacingHub vs RecipeAPI

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseCC BY 4.0 (source data from the F1DB project)Unverified
Free tierFree — no key requiredFree tier — API key required
Rate limit100 req/window · 99 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

RacingHub vs RecipeAPI: common questions

Which is more reliable, RacingHub or RecipeAPI?

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

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

Can I call RacingHub and RecipeAPI from the browser?

Yes — both RacingHub and RecipeAPI send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are RacingHub and RecipeAPI free for commercial use?

RacingHub has unclear commercial terms, and RecipeAPI 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.