Kitsu API

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.