Wiktionary vs Wizard World

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

Uptime · 30d
Uptime · 90d99.44%99.44%
Uptime · 30d100%100%
P50 · ms367350
P95 · ms47094047
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseContent under CC BY-SA 4.0 / GFDLUnverified
Free tierFree — public MediaWiki action APIFree — limits not published
Rate limitNo hard published cap; Wikimedia User-Agent policy and request-etiquette applyUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Wiktionary vs Wizard World: common questions

Which is more reliable, Wiktionary or Wizard World?

Both are neck-and-neck — Wiktionary and Wizard World each measure 99.44% 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, Wiktionary or Wizard World?

Wizard World has the lower median latency in our checks — Wiktionary responds in 367 ms versus Wizard World at 350 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 Wiktionary and Wizard World need an API key?

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

Can I call Wiktionary and Wizard World from the browser?

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

Are Wiktionary and Wizard World free for commercial use?

Wiktionary allows commercial use on its free tier, and Wizard World 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.