Shields vs Wikidata

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms30585
P95 · ms9253283
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Shields vs Wikidata: common questions

Which is more reliable, Shields or Wikidata?

Both are neck-and-neck — Shields and Wikidata 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, Shields or Wikidata?

Shields has the lower median latency in our checks — Shields responds in 30 ms versus Wikidata at 585 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 Shields and Wikidata need an API key?

Neither needs a paid key — Shields is callable with no signup, and Wikidata is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Shields and Wikidata from the browser?

Only Shields is browser-friendly — it returns CORS headers over HTTPS. Wikidata needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Shields and Wikidata free for commercial use?

Shields has unclear commercial terms, and Wikidata 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.