Anime · head-to-head
Kitsu vs MyAnimeList
Kitsu's JSON:API-flavored REST endpoint at kitsu.io/api/edge was confirmed live with an unauthenticated anime listing and an explicit Access-Control-Allow-Origin: * header. Reading the catalog needs no account at all; OAuth is only required for actions tied to a user's own library, and the API itself carries no paid tier.
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.
| Kitsu | MyAnimeList | |
|---|---|---|
| Authentication | OAuth | OAuth |
| Pricing | free | free |
| Formats | JSON | JSON |
| CORS | yes | no |
| HTTPS | Yes | Yes |
Kitsu supports CORS, while MyAnimeList doesn't — pick Kitsu for direct browser calls.