PokéAPI vs Raider

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

Uptime · 30d
Uptime · 90d100%98.9%
Uptime · 30d100%100%
P50 · ms86140
P95 · ms21934160
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial usenounclear
Data licenseFair-use fan dataUnverified (Blizzard game data)
Free tierUnlimited (be reasonable)Free, no API key for public data
Rate limitNone — locally cache please300 req/window · 0 remaining · resets 1787935537
In directory since2026-05-022026-07-05
operationalpartialdownno data

PokéAPI vs Raider: common questions

Which is more reliable, PokéAPI or Raider?

On our scheduled checks, PokéAPI leads on measured uptime — PokéAPI at 100% versus Raider at 98.9% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, PokéAPI or Raider?

PokéAPI has the lower median latency in our checks — PokéAPI responds in 86 ms versus Raider at 140 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 PokéAPI and Raider need an API key?

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

Can I call PokéAPI and Raider from the browser?

Yes — both PokéAPI and Raider 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 PokéAPI and Raider free for commercial use?

PokéAPI is personal/non-commercial only, and Raider 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.