Acoustid API vs ParlayAPI

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

Uptime · 30d
Uptime · 90d0.0%87.5%
Uptime · 30d0.0%87.5%
P50 · ms—211
P95 · ms—1536
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree tier — API key may be required for production
Rate limitUnpublished
In directory since2026-07-052026-10-04
operationalpartialdownno data

Acoustid API vs ParlayAPI: common questions

Which is more reliable, Acoustid API or ParlayAPI?

On our scheduled checks, ParlayAPI leads on measured uptime — Acoustid API at 0.0% versus ParlayAPI at 87.5% 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 Acoustid API and ParlayAPI need an API key?

Both ask you to authenticate — Acoustid API uses an API key and ParlayAPI uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call Acoustid API and ParlayAPI from the browser?

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

Are Acoustid API and ParlayAPI free for commercial use?

Acoustid API has unclear commercial terms, and ParlayAPI 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.