AniAPI

Name: AniAPI API
Brand: AniAPI
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaVideo Processingbearer17 EndpointsREST

For Agents

Look up anime titles, episodes, opening/ending songs, and streaming-resource links via AniAPI. Returns cross-platform IDs (MAL, AniList, Kitsu) so agents can stitch results into other anime catalogues.

Install Jentic One Beta

Connect the AniAPI to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AniAPI, 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 AniAPI API.

Search and retrieve anime titles with cross-platform IDs for MyAnimeList, AniList, and Kitsu

List episodes for a given anime including release dates and stream availability

Look up opening and ending theme songs tied to specific anime and episode ranges

GET STARTED

Start building with AniAPI API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AniAPI API for, with concrete tasks.

★ Anime Recommendation Chatbot

Power a Discord or web chatbot that recommends anime by genre, recency, or random pick using GET /anime and GET /random/anime/{count}. The bot returns titles, descriptions, and cross-platform IDs so users can add the recommendation to their MyAnimeList or AniList account in one step. Latency is suitable for interactive chat because each lookup is a single JSON response.

Call GET /random/anime/3 to fetch three random anime, then format the titles, MAL IDs, and synopses into a chat reply

Cross-Platform Watch History Sync

Synchronise a user's watch progress between AniAPI and other tracker platforms by reading and writing to the /user_story endpoints. Agents can fetch a user's current status, episode count, and score, compare it against MyAnimeList or AniList, and push updates back to AniAPI when the user finishes new episodes. Authentication uses a JWT issued via the AniAPI auth flow.

Call GET /user_story for the authenticated user, identify entries where the local MAL count is higher, and POST updated progress back to /user_story

Streaming Link Resolver

Resolve where a given episode can legally be watched by querying GET /resources for an anime or episode ID. The API returns provider links (Crunchyroll, Funimation, etc.) so agents can deep-link users to the correct stream rather than asking them to search manually. Useful for review surfaces, watch-party bots, or aggregator sites.

Look up the anime by title via GET /anime, then call GET /resources/{id} for the desired episode and return the matching provider URL

AI Agent Anime Lookup via Jentic

An AI agent answering anime-related questions can use AniAPI through Jentic to fetch metadata, episodes, songs, and streaming links without managing JWTs directly. Jentic's intent search routes the agent to the correct AniAPI operation with its full input schema, and the JWT is loaded from the vault at execution time so it never enters the agent's context.

Search Jentic for 'find anime by title', load GET /anime, and execute with the user-supplied title to return MAL/AniList/Kitsu IDs and synopsis

Key Endpoints

17 endpoints — jentic publishes the only available openapi specification for aniapi, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/anime

Search and list anime titles

GET

/anime/{id}

Retrieve a single anime by ID

GET

/episode

List episodes across anime

GET

/song

Search opening and ending songs

GET

/resources/{id}

Fetch streaming links for an episode

GET

/user_story

Retrieve a user's anime watch story

GET

/random/anime/{count}

Return random anime for discovery

GET

/auth/me

Return the authenticated user's profile

GET

/anime

Search and list anime titles

GET

/anime/{id}

Retrieve a single anime by ID

GET

/episode

List episodes across anime

GET

/song

Search opening and ending songs

GET

/resources/{id}

Fetch streaming links for an episode

GET

Why Jentic?

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

Credential isolation

AniAPI JWTs are stored encrypted in the Jentic vault. Agents receive scoped execution access only — the raw JWT never enters the agent's prompt or tool context, which matters because AniAPI tokens grant read/write access to a user's watch story.

Intent-based discovery

Agents search by intent (e.g., 'find anime by title') and Jentic returns the matching AniAPI operation with its parameter schema, so the agent can call /anime or /resources without browsing AniAPI's docs.

Time to first call

Direct AniAPI integration: 1-2 days for OAuth handshake, JWT refresh, and error handling. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using AniAPI API through Jentic.

Why is there no official OpenAPI spec for AniAPI?

AniAPI does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AniAPI via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does AniAPI use?

AniAPI uses HTTP bearer authentication with a JWT issued through its OAuth flow. Public read operations on /anime, /episode, and /song typically work unauthenticated, but /user_story and /auth/me require a user-scoped JWT. Through Jentic the JWT is stored in the encrypted vault and is never injected into the agent's prompt context.

Can I update a user's watch history with AniAPI?

Yes. The /user_story endpoint supports reading and updating watch progress, status, and score for a given anime, scoped to the authenticated user identified by the JWT.

What are the rate limits for AniAPI?

The OpenAPI spec does not declare explicit rate limits. AniAPI is community-run, so treat it as best-effort: cache responses for catalogue lookups and back off on 429 or 5xx responses rather than retrying tightly.

How do I look up an anime by title with AniAPI through Jentic?

Run pip install jentic, then search Jentic for 'find anime by title'. Jentic returns GET /anime with its query parameter schema. Execute the call with your title string and parse the returned MyAnimeList, AniList, and Kitsu IDs.

Does AniAPI return streaming provider links?

Yes. GET /resources and GET /resources/{id} return streaming-resource entries for an anime or episode, including provider names and URLs where available. Coverage depends on what the AniAPI community has indexed for that title.