Attack on Titan API vs AnimeChan

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

Attack on Titan API vs AnimeChan: common questions

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

Only AnimeChan is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

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

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

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

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

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