HasData: Structured Web Data APIs vs Wikipedia REST

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY-SA 4.0
Free tierFree tier — API key requiredUnlimited within etiquette
Rate limitUnpublished200/sec global courtesy cap
In directory since2026-07-052026-05-09
operationalpartialdownno data

HasData: Structured Web Data APIs vs Wikipedia REST: common questions

Which is more reliable, HasData: Structured Web Data APIs or Wikipedia REST?

On our scheduled checks, Wikipedia REST leads on measured uptime — HasData: Structured Web Data APIs at —% versus Wikipedia REST at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do HasData: Structured Web Data APIs and Wikipedia REST need an API key?

Wikipedia REST needs no key, while HasData: Structured Web Data APIs requires a free API key. If you want to start calling without signup, reach for Wikipedia REST first.

Can I call HasData: Structured Web Data APIs and Wikipedia REST from the browser?

Yes — both HasData: Structured Web Data APIs and Wikipedia REST send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are HasData: Structured Web Data APIs and Wikipedia REST free for commercial use?

HasData: Structured Web Data APIs has unclear commercial terms, and Wikipedia REST allows commercial use on its free tier. 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.