Kavitareader Kavita

Name: Kavita API
Brand: Kavita
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent DeliveryapiKey493 EndpointsREST

For Agents

Manage a self-hosted Kavita library server: search and read series, chapters, collections, reading progress, want-to-read lists, devices, and admin settings. 493 endpoints covering the full reading platform.

Install Jentic One Beta

Connect the Kavita to your agent

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

Browse and search series, chapters, and collections via /api/Series, /api/Chapter, and /api/Collection endpoints

Track and update reading progress, marks, and resume points via reader and account endpoints

Manage personal want-to-read and reading-list curation through /api/WantToRead and related endpoints

GET STARTED

Start building with Kavita API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Kavita, keeping it validated and agent-ready. Kavita is a self-hosted ebook, comic, and manga reader server that exposes a large REST surface (493 endpoints) for managing libraries, series, chapters, collections, want-to-read lists, reading progress, devices, OPDS feeds, scrobbling, and admin operations. The base URL is parameterised because Kavita is self-hosted: clients point at their own server instance. Authentication uses an API key passed in the `x-api-key` header, with JWT-based session tokens layered on top for browser users.

Use Cases

Patterns agents use Kavita API for, with concrete tasks.

★ Personal Library Reading Automation

Power a personal home-server reading workflow: when a new chapter is added to a tracked series, mark it as want-to-read, push a notification, and queue a download to a Kindle. Kavita's endpoints expose every piece of state needed (series, chapters, want-to-read, devices) so a small automation can keep a household's reading queue moving without anyone touching the web UI.

List unread chapters in series {id} via /api/Series/{id} and add the next one to the want-to-read list via the /api/WantToRead endpoint.

Reading Progress Sync Across Devices

Keep reading progress in sync between a phone, laptop, and dedicated ereader by pushing progress events to Kavita and reading them back from another device. The reader endpoints store per-chapter progress with timestamp, page, and percent-read, which is the canonical state Kavita's official clients use; third-party readers can mirror that behaviour via the API.

Update progress for chapter {id} to page 84 via the reader progress endpoint, then read it back from another client.

Library Maintenance and Metadata Refresh

Run library scans and metadata refreshes on a schedule so newly downloaded files appear in Kavita without manual intervention. The /api/Admin and /api/Library endpoints expose scan triggers, last-scan timestamps, and metadata refresh operations, letting a cron-driven script do what otherwise requires an admin UI session.

Trigger a scan for library {id} via the /api/Library scan endpoint and poll for completion.

OPDS and Email Delivery to Ereaders

Expose a curated reading list via OPDS so dedicated ereader apps can subscribe to a personal feed, or push selected chapters to a Kindle email address using Kavita's email delivery endpoints. The /api/Email and OPDS endpoints handle the protocol details so the user just clicks 'send to my Kindle' or subscribes their Moon+ Reader to a feed URL.

Trigger send-to-device for chapter {id} via the /api/Email endpoint targeting the user's saved Kindle address.

Agent-Driven Reading Companion

A personal AI reading companion uses Jentic to query Kavita ('what should I read next?', 'mark today's chapter as read', 'add the new One Piece chapter to my list') and execute the calls. Jentic stores the x-api-key in its vault and points the parameterised base URL at the user's self-hosted server, so secrets never appear in chat with the agent.

Use the Jentic search 'mark a Kavita chapter as read', load the schema, and execute the call for chapter {id}.

Key Endpoints

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

METHOD

PATH

DESCRIPTION

POST

/api/Account/login

POST

/api/Account/refresh-token

Refresh a session token

POST

/api/Account/register

GET

/api/Account

Return the current account profile

POST

/api/Account/reset-password

Reset a user's password

POST

/api/Account/clear-oidc-link

Clear an OIDC link from the account

POST

/api/Account/login

POST

/api/Account/refresh-token

Refresh a session token

POST

/api/Account/register

GET

/api/Account

Return the current account profile

POST

/api/Account/reset-password

Reset a user's password

Why Jentic?

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

Credential isolation

The Kavita API key (`x-api-key`) and any JWT session token are stored encrypted in the Jentic vault. Agents receive scoped execution tokens so the raw key and JWT never appear in prompts or transcripts.

Intent-based discovery

Agents search Jentic by intent (for example, 'mark a Kavita chapter as read') and Jentic returns the matching operation with its parameter schema, removing the need to crawl 493 endpoints in the spec by hand.

Time to first call

Direct Kavita integration: 1-2 days to navigate 493 endpoints, handle JWT refresh, and parse paginated series payloads. Through Jentic: under an hour to call any operation by intent.

FAQs

Specific to using Kavita API through Jentic.

Why is there no official OpenAPI spec for Kavita?

The Kavita project does not ship a hosted OpenAPI specification for third-party consumption. Jentic generates and maintains this spec so that AI agents and developers can call Kavita 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 Kavita API use?

The Kavita API uses an API key in the `x-api-key` header (the spec calls the scheme `AuthKey`). Browser clients can additionally exchange username and password at /api/Account/login for a JWT and refresh it via /api/Account/refresh-token. Through Jentic the API key is encrypted in the vault and injected at execution time.

Can I track reading progress through the Kavita API?

Yes. Kavita exposes per-chapter reading progress endpoints under the reader resource that store page, percent-read, and timestamp. Updating progress from one client and reading it from another is the standard sync mechanism Kavita's official apps use.

What are the rate limits for the Kavita API?

Because Kavita is self-hosted there is no vendor-imposed quota. Throughput is bounded by the user's server CPU, disk, and network. The endpoints are designed for a single household's traffic, so steady use from one or two automations is safely within capacity on a typical NAS or home server.

How do I add a series to my want-to-read list through Jentic?

Run `pip install jentic` and search Jentic for 'add a series to Kavita want-to-read'. Jentic returns the schema for the /api/WantToRead endpoint; supply the series ID, then execute the call. The x-api-key is injected from the Jentic vault.

Does the Kavita API support OPDS for ereader apps?

Yes. Kavita publishes OPDS feeds that ereader apps (Moon+ Reader, KOReader, Aldiko) can subscribe to. The OPDS endpoints sit alongside the REST surface in the spec and authenticate with the same x-api-key value.

Is the Kavita API free to use?

Yes — Kavita is open-source and free for personal use, and so is its API surface. The only cost is the server you run it on.

Kavitareader Kavita

Connect the Kavita to your agent

Capabilities

Start building with Kavita API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs