Anime · head-to-head
MyAnimeList vs Studio Ghibli
MyAnimeList's official v2 REST API was reconfirmed live at api.myanimelist.net/v2 — an unauthenticated request returned a 403 from the real gateway rather than a network error, and a preflight OPTIONS carried no Access-Control-Allow-Origin header, so cors is corrected to no. It requires a registered OAuth 2 client, the same one the community 'Official MAL API' club (the entry's stored url) walks new developers through, and remains completely free to use.
The original ghibliapi.herokuapp.com now returns Heroku's 'No such app' placeholder — Heroku retired free dynos in November 2022 — but the project lives on at the community-maintained ghibliapi.vercel.app mirror, confirmed live with a real films listing and Access-Control-Allow-Origin echoing the request's Origin. It remains a free, keyless, read-only dataset of Ghibli films, people, and locations.
| MyAnimeList | Studio Ghibli | |
|---|---|---|
| Authentication | OAuth | None |
| Pricing | free | free |
| Formats | JSON | JSON |
| CORS | no | yes |
| HTTPS | Yes | Yes |
Studio Ghibli needs no API key, while MyAnimeList requires OAuth — pick Studio Ghibli to start without signup.