Battle.net vs Pokefact API

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms10241757
P95 · ms31732575
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Battle.net vs Pokefact API: common questions

Which is more reliable, Battle.net or Pokefact API?

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

Battle.net has the lower median latency in our checks — Battle.net responds in 1024 ms versus Pokefact API at 1757 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 Battle.net and Pokefact API need an API key?

Pokefact API needs no key, while Battle.net requires a free API key. If you want to start calling without signup, reach for Pokefact API first.

Can I call Battle.net and Pokefact API from the browser?

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

Are Battle.net and Pokefact API free for commercial use?

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