Kitsu API
Agent-ready OpenAPI document · curated by JenticMediaContent Deliveryoauth211 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Look up anime and manga titles, fetch user libraries and progress, and read community reviews from the Kitsu catalogue.
Use for: Find all anime in the Kitsu catalogue matching a title query, Retrieve the manga record with id 1 from Kitsu, Get the user profile and avatar for a given Kitsu username, List all library entries belonging to a Kitsu user
Not supported: Does not handle anime streaming, video playback, or licensing - use for catalogue lookups, user library tracking, and community reviews only.
Kitsu is an anime and manga discovery platform with a JSON:API-compliant catalogue of titles, user profiles, library entries, and reviews. The API exposes anime and manga records, user accounts, library entry tracking (current status, progress, ratings), and community reviews - all backed by the public Kitsu database. It is well suited for building anime trackers, recommendation widgets, fan dashboards, and bots that surface what a user is watching or reading. The specification behind this entry is a curated, agent-optimized variant maintained by Jentic: Kitsu's own OpenAPI document at github.com/hummingbird-me/api-docs describes the anime, manga, episode, and Algolia search-key resources, but not the user, review, and library-entry operations listed here.
Install Jentic One Beta
Connect the Kitsu API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Kitsu API, 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.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fkitsu.io%2Fkitsu" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fkitsu.io%2Fkitsu" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Kitsu API.
Search the Kitsu catalogue for anime by title or season and sort by popularity
Retrieve manga records with synopsis, chapter count, and serialization data
Look up a user profile with name, about text, and avatar on Kitsu
Pull a user's library entries to track watch and read progress
Fetch community reviews attached to a specific anime or manga
Browse paginated lists of anime and manga using JSON:API filters
Use Cases
Patterns agents use Kitsu API for, with concrete tasks.
★ Anime Discovery Widget
Power an anime discovery feature on a fan site or chat bot by querying Kitsu's catalogue at /anime and /anime/{id}. The endpoints return JSON:API resources with synopsis, episode count, average rating, and cover art, so the surface area of a discovery card can be assembled from a single response. Useful for Discord bots, browser extensions, and recommendation widgets that need fresh metadata without scraping.
Call GET /anime with a filter on the title 'Frieren' and return the top result's synopsis, episode count, and average rating.
User Library Tracker
Build a personal anime and manga tracker that mirrors a user's Kitsu library. GET /library-entries takes a required filter[userId] and returns each entry's status (current, planned, completed, on_hold, dropped), progress, and rating, while /users/{id} returns the profile name and avatar to head the dashboard. The spec declares no include parameter on /library-entries, so an agent lists the entries first and then resolves each title with a separate /anime/{id} or /manga/{id} call.
Fetch the library entries for user id 12345 with filter[status]=current, and return the status, progress, and rating for each entry.
Community Review Surface
Surface Kitsu community reviews next to an anime or manga record on a third-party site or in an agent's response. The /reviews endpoint takes filter[animeId] or filter[mangaId] and returns review text, a numeric rating, and a creation timestamp per review, so an agent can summarise community sentiment for a title without needing its own review system. Best for editorial bots and aggregator pages that want to enrich a title page with social signal.
Call GET /reviews with filter[animeId]=1 and page[limit]=5, and return each review's rating and an excerpt of its content.
Agent-Driven Anime Assistant via Jentic
Embed Kitsu lookups in an AI agent through Jentic so that questions like 'what is the user currently watching' or 'find a manga similar to Berserk' resolve to real catalogue data. The agent searches Jentic for the matching Kitsu operation, loads its schema, and executes the call without ever holding raw OAuth tokens. This is faster than wiring Kitsu's JSON:API client into the agent stack directly.
Through Jentic, search for 'find an anime on Kitsu', load the /anime operation, and return the top match for the query 'cyberpunk'.
Key Endpoints
11 endpoints — kitsu is an anime and manga discovery platform with a json:api-compliant catalogue of titles, user profiles, library entries, and reviews.
METHOD
PATH
DESCRIPTION
GET
/anime
List or search anime titles
GET
/anime/{id}
Retrieve a single anime record
GET
/manga
List or search manga titles
GET
/users/{id}
Retrieve a user profile
GET
/library-entries
List a user's library entries
GET
/reviews
List community reviews
GET
/anime
List or search anime titles
GET
/anime/{id}
Retrieve a single anime record
GET
/manga
List or search manga titles
GET
/users/{id}
Retrieve a user profile
GET
/library-entries
List a user's library entries
GET
/reviews
List community reviews
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Kitsu by hand means running its OAuth2 password flow, refreshing the token, and passing it against the kitsu.io/api/edge host yourself. Through Jentic you install once, import Kitsu from the API Directory, store the credential once, and your agent calls it.
Permission scoping
Kitsu carries a record id in the URL path on writes as well as reads (PATCH /library-entries/{id} and DELETE /library-entries/{id} alongside /anime/{id} and /users/{id}), and the PATCH body itself requires type and id, so scope by operation: limit the agent to the operations it needs, such as catalogue lookups, library reads, and community reviews, and leave the library-entry write operations out of the allowed set.
Credential isolation
Your Kitsu credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'look up an anime by title' or 'read a user's library entries', and Jentic returns the matching Kitsu operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Kitsu API through Jentic.
Does Kitsu publish an official OpenAPI specification?
Yes. Kitsu publishes an OpenAPI 3.0.3 document titled 'Kitsu JSON:API Documentation' in its own GitHub organisation at github.com/hummingbird-me/api-docs (api/kitsu.yml on the openapi3 branch). That document describes the anime, manga, episode, and Algolia search-key resources. The specification behind this entry is a curated, agent-optimized variant maintained by Jentic that also covers the user, review, and library-entry operations the vendor's document leaves out, which is why Jentic keeps its own copy.
What authentication does the Kitsu API use?
The Kitsu API uses OAuth 2.0 for authenticated endpoints (user library writes, account-scoped data). Read-only catalogue endpoints such as /anime and /manga can be called without authentication. When called through Jentic, OAuth tokens are stored in your Jentic One instance and never enter the agent's context.
Can I read a user's anime watchlist with the Kitsu API?
Yes. Call GET /library-entries with a filter on user id to retrieve a user's tracked anime and manga, including status, progress, and rating. Combine with /users/{id} to attach profile metadata to the watchlist.
What are the rate limits for the Kitsu API?
Kitsu's published OpenAPI document and its API Blueprint state no request-rate ceiling, and catalogue responses carry no rate-limit or retry-after headers, so treat the ceiling as unspecified rather than absent. What the vendor does document is page size: page[limit] accepts a maximum of 20 resources per request and defaults to 10. Page through results with the JSON:API links.next URL and cache repeated catalogue lookups instead of issuing large bursts.
How do I search for an anime with the Kitsu API through Jentic?
Search Jentic for 'find an anime on Kitsu', load the /anime operation schema, then execute with a filter parameter such as filter[text]=frieren. The agent receives the JSON:API response with title, synopsis, and rating and never has to handle OAuth flows directly.
Is there a Kitsu API MCP server?
You don't need an MCP server to give your agent Kitsu. Jentic connects it directly from the API Directory: import Kitsu, store your OAuth credential once in your own Jentic One instance, and your agent calls the catalogue, library, and review operations it needs without loading another server's tool definitions into its context.
Can I limit what my agent is allowed to do with the Kitsu API?
Yes. Because you run Jentic One yourself, your own rules decide which Kitsu operations the agent can call, so you can grant only the read endpoints it needs, such as catalogue lookups on /anime and /manga, library reads on /library-entries and /users/{id}, and community reviews on /reviews, and leave everything else out of the allowed set. Kitsu's write operations (POST /library-entries, PATCH /library-entries/{id}, DELETE /library-entries/{id}) are separate operations from the reads, so scoping is done at the operation level rather than per record: excluding those three is what keeps the agent read-only. The Kitsu OAuth credential is stored once by your own Jentic One instance and injected at execution time, so the agent never sees the token and can only reach the operations you permit.
GET STARTED