Call of Duty Mobile vs PokéAPI

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

Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d100%100%
P50 · ms331761
P95 · ms41932193
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearno
Data licenseUnverifiedFair-use fan data
Free tierFree — no API keyUnlimited (be reasonable)
Rate limitUnpublishedNone — locally cache please
In directory since2026-07-052026-05-02
operationalpartialdownno data

Call of Duty Mobile vs PokéAPI: common questions

Which is more reliable, Call of Duty Mobile or PokéAPI?

On our scheduled checks, PokéAPI leads on measured uptime — Call of Duty Mobile at 99.02% versus PokéAPI at 100% 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, Call of Duty Mobile or PokéAPI?

PokéAPI has the lower median latency in our checks — Call of Duty Mobile responds in 3317 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 Call of Duty Mobile and PokéAPI need an API key?

Neither needs a paid key — Call of Duty Mobile 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 Call of Duty Mobile and PokéAPI from the browser?

Only PokéAPI is browser-friendly — it returns CORS headers over HTTPS. Call of Duty Mobile needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Call of Duty Mobile and PokéAPI free for commercial use?

Call of Duty Mobile 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.