shipapis
StarSubmit an APISubmit API

Agify vs Studio Ghibli API

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

APIAgifyHEALTHY89Studio Ghibli APIHEALTHY100
Uptime · 30d
Uptime · 90d93.1%100%
Uptime · 30d91.7%100%
P50 · ms54575
P95 · ms1337278
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseProprietaryUnverified
Free tier100 names/day, no signupFree — limits not published
Rate limit100/day per IPUnpublished
In directory since2026-05-022026-07-05
operationalpartialdownno data

Agify vs Studio Ghibli API: common questions

Which is more reliable, Agify or Studio Ghibli API?

On our scheduled checks, Studio Ghibli API leads on measured uptime — Agify at 93.1% versus Studio Ghibli 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, Agify or Studio Ghibli API?

Studio Ghibli API has the lower median latency in our checks — Agify responds in 545 ms versus Studio Ghibli API at 75 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 Agify and Studio Ghibli API need an API key?

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

Can I call Agify and Studio Ghibli API from the browser?

Yes — both Agify and Studio Ghibli 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 Agify and Studio Ghibli API free for commercial use?

Agify allows commercial use on its free tier, and Studio Ghibli 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.