HTTP Dog vs iNaturalist

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

HTTP Dog vs iNaturalist: common questions

Which is more reliable, HTTP Dog or iNaturalist?

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

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

Can I call HTTP Dog and iNaturalist from the browser?

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

Are HTTP Dog and iNaturalist free for commercial use?

HTTP Dog has unclear commercial terms, and iNaturalist 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.