Geocoder REST API vs What The Commit

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms7391312
P95 · ms13024279
AuthapiKeynone
CORSnoyes
HTTPSyesno
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 What The Commit: common questions

Which is more reliable, Geocoder REST API or What The Commit?

On our scheduled checks, Geocoder REST API leads on measured uptime — Geocoder REST API at 100% versus What The Commit at 99.02% 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 What The Commit?

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

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

Can I call Geocoder REST API and What The Commit from the browser?

Neither sends browser-friendly CORS headers reliably, so call Geocoder REST API and What The Commit from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Geocoder REST API and What The Commit free for commercial use?

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