shipapis
StarSubmit an APISubmit API

xeno-canto vs HTTP Dog

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

APIxeno-cantoNEW—HTTP DogNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
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

xeno-canto vs HTTP Dog: common questions

Which is more reliable, xeno-canto or HTTP Dog?

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

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

Can I call xeno-canto and HTTP Dog from the browser?

Only xeno-canto 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 xeno-canto and HTTP Dog free for commercial use?

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