AnimeChan vs Attack on Titan API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

AnimeChan vs Attack on Titan API: common questions

Which is more reliable, AnimeChan or Attack on Titan API?

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

Do AnimeChan and Attack on Titan API need an API key?

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

Can I call AnimeChan and Attack on Titan API from the browser?

Yes — both AnimeChan and Attack on Titan 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 AnimeChan and Attack on Titan API free for commercial use?

AnimeChan has unclear commercial terms, and Attack on Titan 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.