Keyvalue vs MangaTranslate API

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

Uptime · 30d
Uptime · 90d92.1%100%
Uptime · 30d100%100%
P50 · ms427330
P95 · ms3359876
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-07-052026-10-04
operationalpartialdownno data

Keyvalue vs MangaTranslate API: common questions

Which is more reliable, Keyvalue or MangaTranslate API?

On our scheduled checks, MangaTranslate API leads on measured uptime — Keyvalue at 92.1% versus MangaTranslate 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, Keyvalue or MangaTranslate API?

MangaTranslate API has the lower median latency in our checks — Keyvalue responds in 427 ms versus MangaTranslate API at 330 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 Keyvalue and MangaTranslate API need an API key?

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

Can I call Keyvalue and MangaTranslate API from the browser?

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

Are Keyvalue and MangaTranslate API free for commercial use?

Keyvalue has unclear commercial terms, and MangaTranslate 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.