Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the ListOfBooks 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%2Flistofbooks.net%2Flistofbooks" | shStep 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%2Flistofbooks.net%2Flistofbooks" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with ListOfBooks API.
Search book series by name with search-series, returning up to 5 matches that each link to a reading-order page
Fetch the reading order of one series by name with get-reading-order
Find which series a book belongs to, and its position, from a title and author with find-series-for-book
List the titles of up to 25 series an author wrote with get-author-series
GET STARTED
Search authors by name with search-authors and get a link to each author page
Patterns agents use ListOfBooks API for, with concrete tasks.
★ Reading-order answers from an agent through Jentic
A reading assistant agent connected through Jentic searches by intent for a series reading order, gets the get-reading-order operation with its schema, and calls it with the series name. It returns the books in order with a link to the listofbooks.net page, so the user gets a sourced answer rather than a guessed list.
Call GET /api/public/v1/get-reading-order with series 'The Expanse' and return the ordered titles with the page url
Identify the series behind a single book
When a user names one book, an agent calls find-series-for-book with the book's title and author to learn which series it belongs to, its position, and the full series order. This lets a library or bookshop assistant tell a reader which book to pick up next.
Call GET /api/public/v1/find-series-for-book with title 'Leviathan Wakes' and author 'James S. A. Corey', then report the series and the book's position
Author bibliography by series
A library assistant agent calls get-author-series with an author name to get the best-matching author and the titles of the series they wrote, then calls get-reading-order for each title. The result is a series-by-series reading guide for that author with links to each page.
Call GET /api/public/v1/get-author-series with author 'Terry Pratchett', then call GET /api/public/v1/get-reading-order for the first returned series title
5 endpoints — the listofbooks api looks up book series, reading orders, and authors from the listofbooks.
METHOD
PATH
DESCRIPTION
/api/public/v1/search-series
Search book series
/api/public/v1/get-reading-order
Get a series reading order
/api/public/v1/find-series-for-book
Find the series a book belongs to
/api/public/v1/get-author-series
List an author's series
/api/public/v1/search-authors
Search authors
/api/public/v1/search-series
Search book series
/api/public/v1/get-reading-order
Get a series reading order
/api/public/v1/find-series-for-book
Find the series a book belongs to
/api/public/v1/get-author-series
List an author's series
/api/public/v1/search-authors
Search authors
What agents get from Jentic-routed access to this vendor.
Setup
Wiring ListOfBooks by hand means getting a free key, picking between the bearer and X-API-Key header forms, and tracking its shared call allowances yourself. Through Jentic you install once, import the ListOfBooks API from the API Directory, store the key once, and your agent calls it.
Permission scoping
ListOfBooks takes the series, author, or book title as a query parameter, so rules bound which operations your agent may call, not which series it looks up. Every operation is a read-only lookup, so scoping here is about choosing which lookups the agent may spend your shared allowance on.
Credential isolation
Your ListOfBooks API key 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 'reading order of a book series' or 'which series is this book in', and Jentic returns the matching ListOfBooks operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using ListOfBooks API through Jentic.
What authentication does the ListOfBooks API use?
Per its OpenAPI spec, each call takes a free API key from the listofbooks.net developers page, sent either as a bearer token in the Authorization header or in the X-API-Key header. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.
What are the rate limits for the ListOfBooks API?
The spec states that a free key allows 10 calls per minute, 60 per hour, and 200 per day, plus 50 distinct series or author pages per day, and all keys of one member share these limits. Responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers so an agent can pace itself.
Can I find which series a book belongs to with the ListOfBooks API?
Yes. GET /api/public/v1/find-series-for-book takes a book's title and author, both required, and returns the series it belongs to, its position, and the series order with a link to the series page.
Is there a ListOfBooks MCP server?
You don't need an MCP server to give your agent the ListOfBooks API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls it. Operations are found by intent when needed, so no extra tool definitions sit in your agent's context.
How do I get a series reading order through Jentic?
Install Jentic One, add the ListOfBooks API from the directory, and store your free key. Your agent then searches for 'reading order of a book series', gets GET /api/public/v1/get-reading-order with its schema, and calls it with the series name. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the ListOfBooks API?
Yes. Write a rule that allows only get-reading-order and find-series-for-book, so the agent can answer reading-order questions but cannot run open-ended series or author searches that use up your daily page allowance, and every call it makes is logged.
For Agents
Answer 'what order should I read this series in' questions: search book series and authors, get a series reading order, list an author's series, and find the series a book belongs to.
Use for: What order should I read the Discworld books in, Find the series that 'The Fellowship of the Ring' belongs to, List all series written by Brandon Sanderson, Search for an author page on listofbooks.net
Not supported: Does not handle book purchases, ISBN or edition metadata, reviews, or e-book content. Use for book series, reading order, and author series lookups only.
The ListOfBooks API looks up book series, reading orders, and authors from the listofbooks.net database, and every result links back to its page on the site. Agents can search series or authors by name, fetch the reading order of one series, list the series an author wrote, or find which series a given book belongs to and where it sits in the order. All five operations are read-only GET lookups that take a free API key.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>