Install Jentic One Beta

Connect the MangaUpdates API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the MangaUpdates 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmangaupdates.com%2Fmangaupdates" | sh

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%2Fmangaupdates.com%2Fmangaupdates" | 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 MangaUpdates API.

Search series with POST /series/search by title, genre, exclude_genre, category, type, year, and licensed status, sorted with orderby

Retrieve a series by id along with the scanlation groups working on it, its rating rainbow, and its edit history

Find new chapter releases by day with GET /releases/days, or follow a series through its RSS release feed

Look up authors, publishers, and scanlation groups and list the series each one is linked to

GET STARTED

Start building with MangaUpdates API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use MangaUpdates API for, with concrete tasks.

★ Manga lookup and tracking agent through Jentic

A reading assistant searches MangaUpdates for a series, reports its groups and latest releases, and updates the member's reading list as chapters are read. Through Jentic the agent finds these operations by intent among the API's large surface, the member's session token stays in the developer's own Jentic One instance, and a rule can keep the agent on search and list updates while moderation and account operations stay out.

POST /series/search with search 'Vinland Saga', then GET /series/{id}/groups for the top result, then POST /lists/series/update with the series id and status chapter 42

Release monitoring

Readers following many series want to know when new chapters appear. GET /releases/days lists releases by day with optional include_metadata, GET /series/{id}/rss provides a per-series feed, and POST /releases/search narrows releases by group_id or a start_date and end_date range.

Call GET /releases/days with include_metadata true and report each release's series title and chapter

Series research for recommendations

Recommendation tools need structured series data. POST /series/search filters by genre, category, type, and year, POST /authors/search and POST /publishers/search find creators and publishers, and POST /authors/{id}/series and GET /publishers/{id}/series list the works tied to each, so a tool can suggest similar titles by the same author or imprint.

POST /authors/search with search 'Naoki Urasawa', then POST /authors/{id}/series for the matching author and list the titles

Key Endpoints

249 endpoints — the mangaupdates api powers the mangaupdates manga database and community, exposing series, authors, publishers, scanlation groups, and chapter releases alongside reviews, forums, and user reading lists.

METHOD

PATH

DESCRIPTION

POST

/series/search

Search series

GET

/series/{id}

Get a specific series

GET

/series/{id}/groups

List groups scanlating a series

GET

/releases/days

Show releases by day

POST

/authors/search

Search authors

POST

/lists/series

Add a series to a list

PUT

/series/{id}/rating

Update the user rating for a series

PUT

/account/login

Create a session token

POST

/series/search

Search series

GET

/series/{id}

Get a specific series

GET

/series/{id}/groups

List groups scanlating a series

GET

/releases/days

Show releases by day

POST

/authors/search

Search authors

POST

/lists/series

Add a series to a list

PUT

/series/{id}/rating

Update the user rating for a series

PUT

/account/login

Create a session token

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring MangaUpdates by hand means logging in with PUT /account/login to get a JWT session token, refreshing it, and paging through the search operations yourself. Through Jentic you install once, import MangaUpdates from the API Directory, store the credential once, and your agent calls it.

Permission scoping

MangaUpdates puts series, author, and list ids in the URL path, so a rule can pin your agent to one series or one list and the operations you pick. You choose the operations it may call, so destructive ones like DELETE /series/{id} or member and moderation operations are not included unless you add them.

Credential isolation

Your MangaUpdates session token 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 'search manga series' or 'list today's releases', and Jentic returns the matching MangaUpdates operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using MangaUpdates API through Jentic.

Is there a MangaUpdates MCP server?

You don't need an MCP server to give your agent MangaUpdates. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls it. Operations are discovered on demand, so the API's large surface does not load as tool definitions into the agent's context.

What authentication does the MangaUpdates API use?

Per its OpenAPI spec, the MangaUpdates API declares bearer authentication with a JWT session token in the Authorization header. You get a session token from PUT /account/login with your username and password, and registration happens on the main website rather than through the API. Through Jentic the token is stored encrypted by your own Jentic One instance and injected at execution time, so it never enters the agent's context.

Can I limit what my agent is allowed to do with MangaUpdates?

Yes. For example, write a rule that allows POST /series/search, GET /series/{id}, and GET /releases/days, so the agent can look up series and releases but cannot change your lists, post in forums, or touch moderation operations. Every call it makes is logged on your own machine.

How do I track reading progress through Jentic?

Install Jentic One, import the MangaUpdates API from the directory, and search for 'update my manga reading list'. Jentic returns the list series update operation with its input schema; your agent sends the series id with a status volume or chapter. To run it on your own infrastructure, install Jentic One from its GitHub repo.

What are the rate limits for the MangaUpdates API?

The OpenAPI spec does not state a numeric rate limit. Its acceptable use policy asks you to space requests reasonably so as not to overwhelm the MangaUpdates servers and to cache data. Check https://www.mangaupdates.com for current terms.

Can I use MangaUpdates data in my own app?

The acceptable use policy in the spec requires you to credit MangaUpdates when using its data, and bans uses that deceive users, create spam, assist illegal actions, or damage the database. MangaUpdates makes no warranties about availability or correctness of the data.

MangaUpdates API

AI ReadinessFoundational (C)55/100

See full scorecard

Official vendor OpenAPI document · agent-readyMediaContent Deliverybearer249 EndpointsREST

For Agents

Search the MangaUpdates database for manga series, authors, publishers, groups, and releases, and for a signed-in member, rate series and track reading progress in lists.

Use for: Search MangaUpdates for completed action manga from 2015, Find which scanlation groups are working on this series, List all manga releases published today, Get the series written by a specific author

Not supported: Does not handle reading chapter pages, selling or licensing manga, or anime tracking. Use for searching manga series and release data and managing a member's MangaUpdates lists and ratings only.

The MangaUpdates API powers the MangaUpdates manga database and community, exposing series, authors, publishers, scanlation groups, and chapter releases alongside reviews, forums, and user reading lists. It searches series by title, genre, category, type, and year, returns series details with the groups scanlating them and their ratings, and lists releases by day or as an RSS feed. Signed-in members can rate series, track volume and chapter progress in reading lists, and post in forums and conversations. Data use requires crediting MangaUpdates and spacing requests reasonably under its acceptable use policy.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

92%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B-Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

46%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

26%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

98%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

58%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: D-Signals: 1

43%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: A-Signals: 1

75%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: C-Signals: 1

52%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the MangaUpdates API to your agent

Capabilities

Start building with MangaUpdates API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

MangaUpdates API

Jentic AI Readiness Score

MangaUpdates API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness