RandomDuck vs xeno-canto
Same instrument, two spec sheets — measured, not claimed.
RandomDuck vs xeno-canto: common questions
Which is more reliable, RandomDuck or xeno-canto?
Both are neck-and-neck — RandomDuck 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, RandomDuck or xeno-canto?
RandomDuck has the lower median latency in our checks — RandomDuck responds in 459 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 RandomDuck and xeno-canto need an API key?
Neither needs a paid key — RandomDuck 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 RandomDuck and xeno-canto from the browser?
Only xeno-canto is browser-friendly — it returns CORS headers over HTTPS. RandomDuck needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are RandomDuck and xeno-canto free for commercial use?
RandomDuck 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.