APIClaw vs PubMed E-utilities

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

Uptime · 30d
Uptime · 90d100%63.9%
Uptime · 30d100%50.0%
P50 · ms661389
P95 · ms7004903
AuthapiKeynone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limit3 req/window · 1 remaining
In directory since2026-10-302026-07-05
operationalpartialdownno data

APIClaw vs PubMed E-utilities: common questions

Which is more reliable, APIClaw or PubMed E-utilities?

On our scheduled checks, APIClaw leads on measured uptime — APIClaw at 100% versus PubMed E-utilities at 63.9% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, APIClaw or PubMed E-utilities?

PubMed E-utilities has the lower median latency in our checks — APIClaw responds in 661 ms versus PubMed E-utilities at 389 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 APIClaw and PubMed E-utilities need an API key?

PubMed E-utilities needs no key, while APIClaw requires a free API key. If you want to start calling without signup, reach for PubMed E-utilities first.

Can I call APIClaw and PubMed E-utilities from the browser?

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

Are APIClaw and PubMed E-utilities free for commercial use?

APIClaw has unclear commercial terms, and PubMed E-utilities 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.