MeowFacts vs xeno-canto

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms576752
P95 · ms30551457
Authnonenone
CORSyesyes
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

MeowFacts vs xeno-canto: common questions

Which is more reliable, MeowFacts or xeno-canto?

Both are neck-and-neck — MeowFacts 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, MeowFacts or xeno-canto?

MeowFacts has the lower median latency in our checks — MeowFacts responds in 576 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 MeowFacts and xeno-canto need an API key?

Neither needs a paid key — MeowFacts 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 MeowFacts and xeno-canto from the browser?

Yes — both MeowFacts and xeno-canto 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 MeowFacts and xeno-canto free for commercial use?

MeowFacts 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.