Shields vs Wikipedia REST

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms3098
P95 · ms925961
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY-SA 4.0
Free tierFree — limits not publishedUnlimited within etiquette
Rate limitUnpublished200/sec global courtesy cap
In directory since2026-07-052026-05-09
operationalpartialdownno data

Shields vs Wikipedia REST: common questions

Which is more reliable, Shields or Wikipedia REST?

Both are neck-and-neck — Shields and Wikipedia REST 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 Wikipedia REST?

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

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

Can I call Shields and Wikipedia REST from the browser?

Yes — both Shields 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 Shields and Wikipedia REST free for commercial use?

Shields 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.