shipapis
StarSubmit an APISubmit API

Studio Ghibli API vs TasteDive

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

APIStudio Ghibli APINEW—TasteDiveNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Studio Ghibli API vs TasteDive: common questions

Which is more reliable, Studio Ghibli API or TasteDive?

On our scheduled checks, TasteDive leads on measured uptime — Studio Ghibli API at —% versus TasteDive 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 Studio Ghibli API and TasteDive need an API key?

Studio Ghibli API needs no key, while TasteDive requires a free API key. If you want to start calling without signup, reach for Studio Ghibli API first.

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

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

Are Studio Ghibli API and TasteDive free for commercial use?

Studio Ghibli API has unclear commercial terms, and TasteDive 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.