Pokefact API vs Wynncraft

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1602608
P95 · ms25162505
Authnonenone
CORSyesyes
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

Pokefact API vs Wynncraft: common questions

Which is more reliable, Pokefact API or Wynncraft?

Both are neck-and-neck — Pokefact API and Wynncraft 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, Pokefact API or Wynncraft?

Wynncraft has the lower median latency in our checks — Pokefact API responds in 1602 ms versus Wynncraft at 608 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 Pokefact API and Wynncraft need an API key?

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

Can I call Pokefact API and Wynncraft from the browser?

Yes — both Pokefact API and Wynncraft 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 Pokefact API and Wynncraft free for commercial use?

Pokefact API has unclear commercial terms, and Wynncraft 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.