AniPub API vs Attack on Titan API

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

Uptime · 30d
Uptime · 90d96.7%100%
Uptime · 30d90.0%100%
P50 · ms638493
P95 · ms16021572
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit60 req/window · 59 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

AniPub API vs Attack on Titan API: common questions

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

On our scheduled checks, Attack on Titan API leads on measured uptime — AniPub API at 96.7% versus Attack on Titan 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, AniPub API or Attack on Titan API?

Attack on Titan API has the lower median latency in our checks — AniPub API responds in 638 ms versus Attack on Titan API at 493 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 AniPub API and Attack on Titan API need an API key?

Neither needs a paid key — AniPub API 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 AniPub API and Attack on Titan API from the browser?

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

Are AniPub API and Attack on Titan API free for commercial use?

AniPub API 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.