24 Pull Requests vs Geocoder REST API

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms678739
P95 · ms27851302
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

24 Pull Requests vs Geocoder REST API: common questions

Which is more reliable, 24 Pull Requests or Geocoder REST API?

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

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

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

Can I call 24 Pull Requests and Geocoder REST API from the browser?

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

Are 24 Pull Requests and Geocoder REST API free for commercial use?

24 Pull Requests has unclear commercial terms, and Geocoder REST 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.