Geocoder REST API vs REST API Beispiele

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

Uptime · 30d
Uptime · 90d100%99.44%
Uptime · 30d100%98.3%
P50 · ms434305
P95 · ms13021398
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 REST API Beispiele: common questions

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

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

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

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

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

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

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