shipapis
StarSubmit an APISubmit API

AniPub API vs Kitsu

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

APIAniPub APIHEALTHY89KitsuHEALTHY98
Uptime · 30d
Uptime · 90d96.7%99.44%
Uptime · 30d90.0%98.3%
P50 · ms638224
P95 · ms16021355
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 Kitsu: common questions

Which is more reliable, AniPub API or Kitsu?

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

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

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

Can I call AniPub API and Kitsu from the browser?

Only Kitsu 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 Kitsu free for commercial use?

AniPub API has unclear commercial terms, and Kitsu 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.