shipapis
StarSubmit an APISubmit API

HTTP Dog vs xeno-canto

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

APIHTTP DogHEALTHY100xeno-cantoHEALTHY90
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms57752
P95 · ms3641457
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 xeno-canto: common questions

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

Both are neck-and-neck — HTTP Dog and xeno-canto each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, HTTP Dog or xeno-canto?

HTTP Dog has the lower median latency in our checks — HTTP Dog responds in 57 ms versus xeno-canto at 752 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 HTTP Dog and xeno-canto need an API key?

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

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

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