MyAnimeList API (beta ver.)

Name: MyAnimeList API (beta ver.) API
Brand: MyAnimeList API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent Deliveryoauth2, apiKey18 EndpointsREST

For Agents

Search MyAnimeList anime and manga, read user list status, and update or delete entries on a user's anime or manga list. Returns catalog and list data across 18 operations.

Install Jentic One Beta

Connect the MyAnimeList API (beta ver.) to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MyAnimeList API (beta ver.), or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with MyAnimeList API (beta ver.) API.

Search and list anime in the MyAnimeList catalog

Read detailed metadata for a specific anime or manga title

Pull the seasonal anime lineup for a given year and season

GET STARTED

Start building with MyAnimeList API (beta ver.) API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use MyAnimeList API (beta ver.) API for, with concrete tasks.

★ Anime Discovery and Recommendation

Build a discovery experience that surfaces seasonal releases and personalized suggestions for an authenticated MyAnimeList user. GET /anime/season/{year}/{season} returns the current seasonal lineup; GET /anime/suggestions returns suggestions tailored to the user's existing list. Together they power 'what to watch this season' modules without operating a recommendation pipeline.

Call GET /anime/season/{year}/{season} for the current quarter and GET /anime/suggestions, then merge results into a discovery feed for the authenticated user.

Personal List Sync from Another Tracker

Sync watch progress recorded in another anime tracker into MyAnimeList so the user's MAL profile stays current. PATCH /anime/{anime_id}/my_list_status updates status, score, and episode count; DELETE /anime/{anime_id}/my_list_status removes an entry. The same flow works for manga via the manga endpoints.

For each watch event in the source tracker, call PATCH /anime/{anime_id}/my_list_status with the new episode count and status.

Top Anime Leaderboard

Render top-ranked anime and manga lists for a community site or fan portal. GET /anime/ranking and GET /manga/ranking return ranked lists by category (all-time, by popularity, airing, upcoming). The lists update automatically as MyAnimeList recomputes rankings, so consumer pages stay current without manual editorial work.

Call GET /anime/ranking with ranking_type=all to render the top 50 anime, then GET /manga/ranking for the manga side.

Forum Topic Reader

Embed MyAnimeList forum boards and topic threads into a community dashboard. GET /forum/boards lists boards; GET /forum/topics lists topics for a board; GET /forum/topic/{topic_id} returns a topic's posts. This lets a fan site surface MAL discussions without scraping the forum HTML.

Call GET /forum/boards, then GET /forum/topics for the selected board and render the topic list with links to GET /forum/topic/{topic_id} for full posts.

AI Agent Anime Tracking Assistant

Equip a Jentic-driven assistant that updates the user's MyAnimeList entries as they describe what they watched. The agent searches Jentic for 'update MyAnimeList anime status', loads PATCH /anime/{anime_id}/my_list_status, and submits the update. Jentic handles the OAuth flow plus the X-MAL-CLIENT-ID header so credentials stay out of the agent's prompt.

Through Jentic, search for 'update my anime list status', load PATCH /anime/{anime_id}/my_list_status, and set status=watching with num_watched_episodes=5 for the matching anime ID.

Key Endpoints

18 endpoints — jentic publishes the only available openapi specification for myanimelist api (beta ver.

METHOD

PATH

DESCRIPTION

GET

/anime

Search the anime catalog

GET

/anime/{anime_id}

Get anime details

GET

/anime/ranking

Get anime ranking

GET

/anime/season/{year}/{season}

Get seasonal anime

GET

/anime/suggestions

Get anime suggestions for the user

PATCH

/anime/{anime_id}/my_list_status

Update anime list status

DELETE

/anime/{anime_id}/my_list_status

Delete an anime from the user's list

GET

/manga

Search the manga catalog

GET

/anime

Search the anime catalog

GET

/anime/{anime_id}

Get anime details

GET

/anime/ranking

Get anime ranking

GET

/anime/season/{year}/{season}

Get seasonal anime

GET

/anime/suggestions

Get anime suggestions for the user

PATCH

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your MyAnimeList client id and OAuth access token are stored once, encrypted, by your own Jentic One instance and injected per operation at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list seasonal anime' or 'update my anime list', and Jentic returns the matching MyAnimeList operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using MyAnimeList API (beta ver.) API through Jentic.

Why is there no official OpenAPI spec for MyAnimeList API (beta ver.)?

MyAnimeList does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MyAnimeList API (beta ver.) via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the MyAnimeList API use?

MyAnimeList supports two schemes. Public catalog reads accept the X-MAL-CLIENT-ID header with a client ID alone, while user-scoped operations require OAuth 2.0 with an access token from the MyAnimeList authorization flow. Through Jentic, both credentials are stored in the vault and applied at request time.

Can I update my watch status with the MyAnimeList API?

Yes. PATCH /anime/{anime_id}/my_list_status updates the status, score, and episode count for an anime on the authenticated user's list. Use DELETE on the same path to remove the entry entirely.

How do I get seasonal anime through Jentic?

Through Jentic, search for 'list seasonal anime', load GET /anime/season/{year}/{season}, and pass the year and one of winter/spring/summer/fall. Jentic returns the seasonal list to your agent without exposing the underlying credentials.

What are the rate limits for the MyAnimeList API?

MyAnimeList rate limits are not declared in the OpenAPI spec and are enforced at the gateway. Stay below a few requests per second per client and back off on 429 responses; bulk syncs should run sequentially rather than in parallel.

Does the MyAnimeList API expose forum data?

Yes. GET /forum/boards lists boards, GET /forum/topics lists topics in a board, and GET /forum/topic/{topic_id} returns the posts within a topic. This is useful for surfacing community discussions in a fan portal.

Can I limit what my agent is allowed to do with the MyAnimeList API?

Yes. Because you run Jentic One yourself, your own rules decide which MyAnimeList operations and credentials the agent may use, so it can be given read-only calls like GET /anime and GET /anime/ranking while a write such as PATCH /anime/{anime_id}/my_list_status or a DELETE on that path is excluded unless you add it. Since MyAnimeList puts the anime id in the URL path (/anime/{anime_id}/my_list_status), a rule can also pin the agent to a single anime entry. The stored client ID and OAuth token are injected only for the operations you permit.