shipapis
StarSubmit an APISubmit API

Studio Ghibli API vs JokeAPI

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

APIStudio Ghibli APINEW—JokeAPINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (open-source project)
Free tierFree — limits not publishedFree — no key
Rate limitUnpublished120 requests/minute per IP (per jokeapi.dev docs)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Studio Ghibli API vs JokeAPI: common questions

Which is more reliable, Studio Ghibli API or JokeAPI?

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

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

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

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

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