shipapis
StarSubmit an APISubmit API

OpenCaged Geocoder (Open Source option) vs Web of Science API Expanded

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

APIOpenCaged Geocoder (Open Source option)REACHABLE100Web of Science API ExpandedHEALTHY88
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms519787
P95 · ms10101985
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenCaged Geocoder (Open Source option) vs Web of Science API Expanded: common questions

Which is more reliable, OpenCaged Geocoder (Open Source option) or Web of Science API Expanded?

On our scheduled checks, OpenCaged Geocoder (Open Source option) leads on measured uptime — OpenCaged Geocoder (Open Source option) at 100% versus Web of Science API Expanded 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, OpenCaged Geocoder (Open Source option) or Web of Science API Expanded?

OpenCaged Geocoder (Open Source option) has the lower median latency in our checks — OpenCaged Geocoder (Open Source option) responds in 519 ms versus Web of Science API Expanded at 787 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 OpenCaged Geocoder (Open Source option) and Web of Science API Expanded need an API key?

Both ask you to authenticate — OpenCaged Geocoder (Open Source option) uses an API key and Web of Science API Expanded uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call OpenCaged Geocoder (Open Source option) and Web of Science API Expanded from the browser?

Only OpenCaged Geocoder (Open Source option) is browser-friendly — it returns CORS headers over HTTPS. Web of Science API Expanded needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are OpenCaged Geocoder (Open Source option) and Web of Science API Expanded free for commercial use?

OpenCaged Geocoder (Open Source option) has unclear commercial terms, and Web of Science API Expanded 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.