Geocoder REST API vs PubMed E-utilities

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

Uptime · 30d
Uptime · 90d100%75.5%
Uptime · 30d100%66.7%
P50 · ms7391259
P95 · ms13024903
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublished3 req/window · 1 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

Geocoder REST API vs PubMed E-utilities: common questions

Which is more reliable, Geocoder REST API or PubMed E-utilities?

On our scheduled checks, Geocoder REST API leads on measured uptime — Geocoder REST API at 100% versus PubMed E-utilities at 75.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.

Which is faster, Geocoder REST API or PubMed E-utilities?

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

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

Can I call Geocoder REST API and PubMed E-utilities from the browser?

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

Are Geocoder REST API and PubMed E-utilities free for commercial use?

Geocoder REST API 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.