Product

How Jentic Works

From API assessment to production deployment in four simple steps.

Product Overview

PLATFORM

Jentic OneSelf-hosted, open-source control plane between your agents and any APIAPI DirectoryBrowse 10,000+ APIs ready for AI agent integrationAPI ScorecardAssess your APIs for AI-readiness with automated scoringAgentic SandboxSafely simulate AI agents with your production APIsJenticSign in to the Jentic web app

CAPABILITIES

IntegrationConnect AI agents to your existing systemsWorkflowsDiscover and capture successful agent workflowsGovernanceDefine, observe, and enforce AI policies

TOOLS

Arazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually
Pricing
Developers

GET STARTED

DocumentationGuides and API referenceQuickstartGet up and running in minutes

COMMUNITY

GitHubOpen source projects and examples
Resources
BlogLatest articles and insightsPress & MediaBrand assets and press contactOpen StandardsBuilt on open specs. Never locked in.NewsletterAPIs, AI agents, mixed with architecture and strategy.
Company
About UsOur mission and teamCareersJoin our teamContactGet in touch
Install Jentic OneBook a Demo
How Jentic WorksJentic OneAPI DirectoryAPI ScorecardAgentic SandboxJenticIntegrationWorkflowsGovernanceArazzo UIArazzo Editor
Pricing
DocumentationQuickstartGitHub
BlogPress & MediaOpen StandardsNewsletter
About UsCareersContact
Request a demoInstall Jentic One
Jentic
For Enterprises
  • Product Overview
  • Agentic Sandbox
  • Book a Demo
For Developers
  • Jentic One
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
ISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

Terms & Conditions•Privacy Policy•
© 2026 Jentic. All rights reserved.
APIs / Media / Kitsu API
Kitsu API logo

Kitsu API

★ Only Publicly Available OpenAPI DocumentMediaContent Deliveryoauth211 EndpointsREST

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.

Jentic publishes the only available OpenAPI specification for Kitsu API, keeping it validated and agent-ready. 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.

Jentic One on GithubView OpenAPI Document

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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
2

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 Kitsu API.

Search the Kitsu catalogue for anime by title, slug, or popularity

Retrieve manga records with synopsis, chapter count, and serialization data

Look up a user profile and their library statistics 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. The /users and /library-entries endpoints return current status (watching, completed, dropped), progress, and rating per title, giving a tracker app everything it needs to render a dashboard. Integration takes hours rather than days because the JSON:API format already encodes relationships between users, entries, and titles.

Fetch the library entries for user id 12345, filter to status='current', and return the title slug and progress 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 returns review text, ratings, and author references 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.

List the latest 5 reviews for the anime with id 1 and return their rating and excerpt.

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 — jentic publishes the only available openapi specification for kitsu api, keeping it validated and agent-ready.

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?

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

Credential management

Credential isolation

Kitsu OAuth tokens are stored encrypted in the Jentic vault. Agents receive scoped access to the /library-entries and /users endpoints without raw client_id or refresh tokens entering their context.

Intent-based discovery

Intent-based discovery

Agents search by intent (e.g., 'find an anime', 'list a user library') and Jentic returns the matching Kitsu operation with its JSON:API schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Time to first call

Direct Kitsu integration: 1-2 days for OAuth setup, JSON:API parsing, and pagination. Through Jentic: under 30 minutes — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

MyAnimeList API

→

Larger anime and manga catalogue with the same domain coverage as Kitsu

Choose MyAnimeList when the user needs the broader catalogue or scoring data that drives community rankings; choose Kitsu for JSON:API ergonomics and modern library tracking.

Complementary

Trakt API

→

Tracks live-action TV and film viewing alongside Kitsu's anime focus

Use Trakt when the user also tracks western shows and films; pair with Kitsu so an agent can answer questions across both anime and live-action libraries.

Complementary

TMDB API

→

General movie and TV metadata source for non-anime titles

Use TMDB to enrich an anime page with cast, crew, and image assets that Kitsu does not always carry.

FAQs

Specific to using Kitsu API through Jentic.

Why is there no official OpenAPI spec for Kitsu API?

Kitsu does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Kitsu API 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 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 the Jentic vault 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 does not document a hard public rate limit but throttles aggressive clients. Treat the catalogue endpoints as best-effort and cache results — Jentic's runtime caches identical search responses across agent calls, which reduces upstream traffic substantially.

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 the Kitsu API free to use?

Yes. The Kitsu API is publicly accessible for catalogue reads with no fee. Authenticated user actions require a Kitsu account but no paid plan.

GET STARTED

Start building with Kitsu API

Explore with Jentic
View OpenAPI Document