ISBNdb API

Name: ISBNdb API
Brand: ISBNdb API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentCompany DataapiKey10 EndpointsREST

For Agents

Look up books, authors, publishers, and subjects in the ISBNdb commercial bibliographic database — fetch by ISBN, search by name, or run a global keyword query.

Install Jentic One Beta

Connect the ISBNdb API to your agent

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

Resolve a 10 or 13-digit ISBN to a full book record with title, authors, publisher, and year

Search the catalogue by free-text query and paginate through matching books

Fetch the bibliography of a specific author including all books attributed to them

GET STARTED

Start building with ISBNdb API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for ISBNdb API, keeping it validated and agent-ready. ISBNdb provides programmatic access to a commercial bibliographic database of over 30 million books, authors, publishers, and subjects. Lookup by ISBN, name, or full-text query returns structured records with metadata such as title, author list, publication year, binding, dimensions, and dewey classification. The same API surface is mirrored under the vendor's `main` slug — the `isbndb-api` slug carries the YAML-source variant of the spec.

Use Cases

Patterns agents use ISBNdb API for, with concrete tasks.

★ Library catalogue enrichment

Enrich an internal book catalogue with authoritative bibliographic metadata so search, filtering, and recommendations work against a consistent schema. The agent calls GET /book/{isbn} for each row and merges the response — title, author list, binding, publication year — back into the local record. ISBNdb covers over 30 million titles, which is enough to resolve most consumer and academic catalogues without falling back to manual cleanup.

For each ISBN in the supplied list, call GET /book/{isbn} and write the returned title and authors back to the local record

Author bibliography page generation

Render an author landing page with their full back catalogue without scraping retail sites. The agent calls GET /author/{name} to retrieve the bibliography, then GET /book/{isbn} on each result for cover and binding details. The pipeline finishes in one or two API rounds per author and avoids the legal grey zone of scraping Amazon or Goodreads.

Fetch the bibliography for 'Ursula K Le Guin' and return the 10 most recent titles with publication years

Subject-driven reading list generation

Produce themed reading lists by querying ISBNdb's subject index. The agent retrieves a subject record via GET /subject/{name}, then expands each title with GET /book/{isbn} for full metadata. Useful for educational platforms generating curriculum-aligned reading lists or for retail sites building topical landing pages.

Look up the subject 'climate change' and return the first page of books with their titles, authors, and ISBNs

AI agent answering book metadata questions

An AI agent fielding consumer questions about books needs a structured fact source. Through Jentic the agent searches for 'lookup ISBN' or 'search books by author', loads the matching ISBNdb operation, and returns a verified record instead of a hallucinated one. Pairs naturally with retrieval-augmented generation pipelines that need ground truth for bibliographic citations.

Given the user question 'Who wrote The Dispossessed?', call GET /books/{query} with query='The Dispossessed' and return the top author

Key Endpoints

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

METHOD

PATH

DESCRIPTION

GET

/book/{isbn}

Retrieve a book record by ISBN

GET

/books/{query}

Search books by query

GET

/author/{name}

Retrieve an author and their bibliography

GET

/authors/{query}

Search authors

GET

/publisher/{name}

Retrieve publisher metadata

GET

/subject/{name}

Retrieve a subject heading

GET

/search

Federated search across all ISBNdb resources

GET

/book/{isbn}

Retrieve a book record by ISBN

GET

/books/{query}

Search books by query

GET

/author/{name}

Retrieve an author and their bibliography

GET

/authors/{query}

Search authors

GET

/publisher/{name}

Retrieve publisher metadata

Why Jentic?

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

Credential isolation

ISBNdb x-api-key values are stored encrypted in the Jentic vault. Agents receive a scoped execution token and never see the raw API key.

Intent-based discovery

Agents search by intent (e.g. 'lookup ISBN' or 'search books by author') and Jentic returns the matching ISBNdb operation with its parameter schema — no manual reading of ISBNdb docs.

Time to first call

Direct ISBNdb integration: 2-3 hours to wire the API key header, pagination, and error handling. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

ISBNdb API (main)

Same surface area as the isbndb-api spec, generated from the JSON-source variant

Use the main slug when downstream tooling expects the canonical isbndb.com/main path

Complementary

AbuseIPDB API

Different domain (IP reputation rather than books) — listed only as a reminder that data-enrichment lookups follow the same key-in-header pattern

Reference for the same lookup-by-key pattern; not a substitute for ISBNdb

FAQs

Specific to using ISBNdb API through Jentic.

Why is there no official OpenAPI spec for ISBNdb API?

ISBNdb does not publish an OpenAPI specification on its developer site. Jentic generates and maintains this spec from the live YAML reference so that AI agents and developers can call ISBNdb 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 ISBNdb API use?

ISBNdb uses an API key passed in the x-api-key request header. Keys are issued from the ISBNdb dashboard after subscribing to a plan. Through Jentic the key sits encrypted in the vault and is injected at request time — agents never see the raw value.

Can I look up a book by its 13-digit ISBN?

Yes. Call GET /book/{isbn} with either the 10 or 13-digit ISBN as the path parameter. The response is a single JSON record with title, authors, publisher, and pricing if available.

What are the rate limits for the ISBNdb API?

Rate limits are not declared in the spec. ISBNdb tiers them per subscription plan — Basic, Premium, and Pro — with the higher tiers raising both per-second and daily ceilings. Confirm the plan-specific number before driving large bulk lookups.

How do I search books by query through Jentic?

Search Jentic with the query 'search books in ISBNdb', load the GET /books/{query} operation, and execute it with the search term in the path parameter. The response includes total match count and a paginated list of book records.

Is ISBNdb the same as Open Library or Google Books?

ISBNdb is a separate commercial database. Coverage of recent commercial titles is generally stronger than Open Library, while Google Books offers full-text search that ISBNdb does not. The right choice depends on whether commercial completeness or full-text snippets matters more.