FreeToGame vs PokéAPI

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms33161
P95 · ms5792193
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearno
Data licenseUnverifiedFair-use fan data
Free tierFree, no API key requiredUnlimited (be reasonable)
Rate limitUnpublishedNone — locally cache please
In directory since2026-07-052026-05-02
operationalpartialdownno data

FreeToGame vs PokéAPI: common questions

Which is more reliable, FreeToGame or PokéAPI?

Both are neck-and-neck — FreeToGame and Poké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, FreeToGame or PokéAPI?

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

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

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

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

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