MangaDex API

Name: MangaDex API
Brand: MangaDex API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMediaContent Deliverybearer113 EndpointsREST

For Agents

Search the MangaDex catalogue and read manga chapters — including manga, chapter, cover, author, and scanlation group lookups plus the at-home image server — through a bearer-token REST API.

Install Jentic One Beta

Connect the MangaDex API to your agent

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

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

Search the manga catalogue by title, tag, or content rating with pagination

Pull a manga's chapter feed in reading order across all available languages

Resolve a chapter id to its at-home image server URLs for image delivery

GET STARTED

Start building with MangaDex API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for MangaDex API, keeping it validated and agent-ready. MangaDex is a fan-run, ad-free manga reader and the API exposes its full catalogue — manga, chapters, covers, authors, scanlation groups, custom lists, ratings, and the at-home image delivery network — to client apps, recommendation tools, and reader bots. Endpoints cover discovery (search and feeds), reading (chapter image URLs via the at-home tokens), and account-level features (login, follows, custom lists, ratings) under bearer authentication. The acceptable use policy requires crediting MangaDex and scanlation groups and forbids running ads or paid services on consumers of the API.

Use Cases

Patterns agents use MangaDex API for, with concrete tasks.

★ Build a personal manga reader

A reader app for personal use needs to search the MangaDex catalogue, list chapters, and stream images legally through MangaDex's at-home network. GET /manga supports the search, GET /manga/{id}/feed returns the chapter list, and GET /at-home/server/{chapterId} returns the image hostnames and tokens that the reader uses to fetch pages. Crediting MangaDex and the scanlation group on each chapter is required by the acceptable use policy.

Given the manga id 'a1c7c817-4e59-43b7-9365-09675a149a6f', list the latest 5 English chapters and resolve the image URLs for the most recent one.

Track new chapters for followed titles

A fan tracker watches a list of manga and notifies the user when new chapters drop. The follow list comes from GET /user/follows/manga, and per-title chapter feeds via GET /manga/{id}/feed reveal new chapters with their published-at timestamps. Cross-referencing against a stored last-seen timestamp produces the diff to notify on.

For each manga the user follows, fetch the chapter feed and return any chapters published since the last run.

Recommendation surface for a fan site

Community fan sites use MangaDex's recommendation endpoint to surface 'if you liked X, try Y' panels next to a title page. GET /manga/{id}/recommendation returns related manga ids, which can then be hydrated with covers and titles via GET /manga/{id} and GET /cover. The result is a recommendation row built from MangaDex's own related-titles graph.

Given a manga id, fetch the top 6 recommended manga, hydrate each with title and cover URL, and return the list.

Agent-driven manga discovery assistant

An AI assistant inside a chat or voice interface helps a user find their next read. Through Jentic, the agent searches by intent, calls /manga with the user's preferences (tags, content rating, status), and follows up with /manga/{id}/recommendation. The agent never holds the user's MangaDex bearer token directly — Jentic injects it at call time.

Given a user prompt 'recommend a completed romance manga rated safe', call MangaDex via Jentic and return three suggestions with titles, descriptions, and cover URLs.

Key Endpoints

113 endpoints — jentic publishes the only available openapi specification for mangadex api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/manga

Search the manga catalogue with filters

GET

/manga/{id}

Get a single manga by id

GET

/manga/{id}/aggregate

Get aggregated volume and chapter structure for a manga

GET

/manga/{id}/recommendation

Get recommended related manga

POST

/auth/login

POST

/auth/refresh

Refresh an expired bearer token

GET

/ping

Service health check

GET

/manga

Search the manga catalogue with filters

GET

/manga/{id}

Get a single manga by id

GET

/manga/{id}/aggregate

Get aggregated volume and chapter structure for a manga

GET

/manga/{id}/recommendation

Get recommended related manga

POST

/auth/login

Why Jentic?

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

Credential isolation

MangaDex bearer tokens (and the username/password used to obtain them) are stored encrypted in the Jentic vault. Agents receive a scoped session — raw credentials never enter the prompt context, so leaked transcripts cannot expose user logins.

Intent-based discovery

Agents search Jentic by intent (e.g. 'search the mangadex catalogue') and Jentic returns the matching GET /manga operation with its full query schema, so the agent can call it without reading the MangaDex docs.

Time to first call

Direct MangaDex integration: 1-2 days for auth, at-home URL flow, and pagination. Through Jentic: under an hour — search, load schema, execute.

FAQs

Specific to using MangaDex API through Jentic.

Why is there no official OpenAPI spec for MangaDex API?

MangaDex does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call MangaDex 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 MangaDex API use?

MangaDex uses bearer tokens. POST /auth/login takes a username and password and returns a bearer token, with POST /auth/refresh for renewal. Through Jentic the credentials and resulting bearer token are stored encrypted in the vault — the agent only ever sees a scoped session, not the raw token.

Can I read manga chapter images through the MangaDex API?

Yes, but image bytes are not served from api.mangadex.org. Call GET /at-home/server/{chapterId} to get a signed at-home server URL plus the chapter hash and page filenames; the client then fetches the image bytes from that at-home host. The acceptable use policy requires crediting MangaDex and the scanlation group when displaying chapters.

What are the rate limits for the MangaDex API?

MangaDex enforces global rate limits documented at api.mangadex.org/docs (around 5 requests per second on most endpoints, with stricter limits on search and at-home). Honour 429 responses with the Retry-After header rather than retrying immediately.

How do I search MangaDex through Jentic?

Run pip install jentic, then search Jentic for 'search the mangadex catalogue'. Jentic returns the GET /manga operation with its query parameter schema (title, includedTags, contentRating, status), which you execute to retrieve matching manga records.

Are commercial uses of the MangaDex API allowed?

No. MangaDex's acceptable use policy forbids running ads or paid services on apps and sites that consume the API, and requires crediting MangaDex and scanlation groups. Build personal, fan, or non-commercial tools only.

MangaDex API

Connect the MangaDex API to your agent

Capabilities

Start building with MangaDex API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs