shipapis
StarSubmit an APISubmit API

Geocoder REST API vs InternetDB API

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

APIGeocoder REST APIHEALTHY90InternetDB APIHEALTHY99
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms739133
P95 · ms13022260
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Geocoder REST API vs InternetDB API: common questions

Which is more reliable, Geocoder REST API or InternetDB API?

Both are neck-and-neck — Geocoder REST API and InternetDB API 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, Geocoder REST API or InternetDB API?

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

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

Can I call Geocoder REST API and InternetDB API from the browser?

Only InternetDB API 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 InternetDB API free for commercial use?

Geocoder REST API has unclear commercial terms, and InternetDB API 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.