Book data API

A book data API over Open Library, the Internet Archive's open catalog of tens of millions of editions. One search returns one row per work: title, authors, first publish year, an ISBN-13 where the catalog holds one, publishers, median page count, community rating with its count, edition count and a cover image URL. Field syntax passes straight through — author:tolkien, isbn:9780261102354, subject:fantasy.

Get my free API key See the request

$0.0004 per delivered book · $2 free every month · Failed runs never billed

POST /v1/scraper/collectors/openlibrary_books/run

$ curl $QD/openlibrary_books/run \
    -H "Authorization: Bearer $QD_API_KEY" \
    -d '{}'
{ "status": "done", "count": 10,
  "results": [
    {
      "title": "…",
      "authors": […],
      "first_publish_year": …,
      "isbn": "…" } ],
  "cost": 0.004 }
# 10 books × $0.0004 · nothing delivered, nothing charged

$0.0004 / book5,000 books on the free $2 every month

Semantic inputquery, sort, max_results — no URL lists

Up to 100books per run, pagination handled for you

No browserread over HTTP/TLS — cheaper and faster than rendering

What a book data API does

As an ISBN API it works in both directions: an isbn: query resolves a barcode to its work, and every search row carries an isbn column — 13-digit preferred — which is the join key that lines a catalog row up with retail, library or pricing data. Where the catalog holds no ISBN the field is null rather than guessed.

The raw Open Library API is free and keyless, but it returns edition-level documents with dozens of fields formatted for its own website. This returns works — one row each, with an editions count instead of near-duplicate records — which is the deduplicated grain a book database API should hand a pipeline.

What one book looks like

Every delivered book carries these fields. Nullable means the source did not publish it — the field stays empty instead of being guessed.

Field	Type	What it holds
`rank`	integer	1-based position.
`title`	string	Title.
`authors`	string[]	Authors (up to 5).
`first_publish_year`	integer · nullable	First publication year.
`isbn`	string · nullable	ISBN (13 preferred).
`publishers`	string[]	Publishers (up to 3).
`languages`	string[]	Language codes.
`pages`	integer · nullable	Median page count.
`rating`	number · nullable	Community rating (0-5).
`ratings_count`	integer · nullable	Number of ratings.
`editions`	integer · nullable	Edition count.
`cover_url`	string · nullable	Cover image.
`url`	string	Open Library page.

Inputs

The whole request. Anything you leave out falls back to the default shown in the catalog.

Input	Type	Required	What it does
`query`	string	yes	Title, author:…, isbn:…, subject:….
`sort`	string	no	Result order.
`max_results`	integer	no	How many books to deliver at most (1–100). You pay only for delivered books.

Pricing

Book data API pricing

$0.0004 per delivered book. A run that delivers nothing costs nothing: blocked pages, challenges and retries are on us, and the $2 monthly allowance covers about 5,000 books before you spend anything.

$0.0004per delivered book$0.4 per 1,000 delivered books

5,000 bookson the free allowance$2 every month, no card

Zero rowszero chargeblocks, captchas and retries are on us

−30%on volume tiersthe catalog returns your key's price

Pay as you go

$0/mo

$2 free credit / month
60 requests / min
List unit prices

Starter

$19/mo

$15 free credit / month
300 requests / min
10% off unit prices

Growth

$79/mo

$50 free credit / month
600 requests / min
20% off unit prices

Scale

$299/mo

$250 free credit / month
1,200 requests / min
30% off unit prices

Same wallet, same key and same $2 monthly allowance as every other Data API. Prices are launch pricing read live from the billing config — GET /v1/scraper/collectors returns the price your key actually pays.

Integration

One POST, typed rows

Base URL https://api.quanticdata.io/v1, Bearer auth, the same key as every other Data API. Endpoint: POST /v1/scraper/collectors/openlibrary_books/run.

curl -X POST https://api.quanticdata.io/v1/scraper/collectors/openlibrary_books/run \
  -H "Authorization: Bearer $QD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{}'

import requests

r = requests.post(
    "https://api.quanticdata.io/v1/scraper/collectors/openlibrary_books/run",
    headers={"Authorization": f"Bearer {QD_API_KEY}"},
    json={},
    timeout=120,
)
for row in r.json()["payload"]["results"]:
    print(row)

const res = await fetch(
  "https://api.quanticdata.io/v1/scraper/collectors/openlibrary_books/run",
  {
    method: "POST",
    headers: {
      Authorization: `Bearer ${process.env.QD_API_KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify({}),
  },
);
const { payload } = await res.json();
console.table(payload.results);

claude mcp add quantumproxies \
  -e QUANTUMPROXIES_API_KEY=qd_live_your_key_here \
  -- npx -y quantumproxies-mcp

# then, in the chat:
> run the openlibrary_books collector with

What people build with the book data API

Three shapes of work this endpoint was designed around.

Catalog enrichment

Resolve a list of titles or ISBNs into metadata rows — authors, year, publishers, pages — to fill the gaps in a product or library database.

Author bibliographies

An author: query sorted by new returns a publication table for one writer, edition counts included, without touching a retailer.

Ratings-weighted shortlists

Sort a subject: query by rating and keep ratings_count beside the score, so a recommendation set can be filtered by how many readers the rating rests on.

Book data API versus rolling your own

The differences that actually cost time when you build this in-house.

	DIY scraper	This collector
Lookup key	Fuzzy title matching and hope	Field queries by author, ISBN and subject
Edition sprawl	Dozens of near-identical edition records	One row per work, with an edition count
Ratings	A separate request per work for scores	Rating and count already on the search row

FAQ

Questions we get about the book data API.

Something else? Ask us →

Can I look up a book by ISBN?

Yes — query isbn:9780261102354 and the matching work returns as a normal row. In the other direction, rows carry an ISBN-13 whenever the catalog has one, so book metadata joins onto sales or inventory tables by barcode.

Where does the book data come from?

Open Library, the Internet Archive's community-maintained catalog. Coverage is broad but uneven: fields like page count, rating or ISBN are null where the catalog holds no figure, and the row never pretends otherwise.

Does it return the text of the books?

No — rows are catalog metadata plus a cover image URL, not page content. It builds book datasets and enriches records; reading the books themselves stays on Open Library.

Is there a free book data API?

Every account gets $2 of credit every month with no card, which is about 5,000 delivered books on this endpoint at $0.0004 each. It renews monthly, and a run that delivers nothing is never billed — so a failed or blocked attempt does not eat the allowance.

How much does one run cost?

Multiply the rows you actually receive by $0.0004. A run capped at 100 books — the maximum for this collector — costs $0.04 if every row comes back, and less when the source has fewer. Volume tiers take up to 30% off, and GET /v1/scraper/collectors returns the price your key actually pays.

Run the book data API now

$2 of free credit every month, no card. Your key returns its own prices from GET /v1/scraper/collectors.

Get my free API key