Project Gutenberg book search API

Use the Project Gutenberg book search API to retrieve ebook catalogue entries, author references and source record links. Combine keywords, author, title, subject or language and choose a catalogue order; results identify matching public-domain ebook records and cover links, not the downloaded book contents. Resolve a bibliographic reference, distinguish editions of a work, or assemble a reading catalogue with author and publication identifiers. Catalogue metadata and links do not imply delivery of the book’s full text or unrestricted access to a digital copy. The detail page provides request and response examples, supported parameters, and usage pricing.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
Optional parameters (12)
Keywords matched against titles, authors and subjects.
Author name words, e.g. `austen` or `mark twain`.
Title words.
Subject words, e.g. `detective`.
Language code: `en`, `fr`, `de`, `fi`, `nl`, `es`, `it`, `pt` and others.
Sort order: `downloads` (most downloaded first, default), `release_date` (newest first) or `title`.
Page number (1-based).
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON exports are not exposed.
Native CSV/NDJSON record selector; it has no effect on this JSON-only product.

Sample response

{
  "books": [
    {
      "author": "Jane Austen",
      "cover_small_url": "https://www.gutenberg.org/cache/epub/1342/pg1342.cover.small.jpg",
      "cover_url": "https://www.gutenberg.org/cache/epub/1342/pg1342.cover.medium.jpg",
      "downloads": 220095,
      "id": 1342,
      "release_date": null,
      "title": "Pride and Prejudice",
      "url": "https://www.gutenberg.org/ebooks/1342"
    },
    {
      "author": "Jane Austen",
      "cover_small_url": "https://www.gutenberg.org/cache/epub/26301/pg26301.cover.small.jpg",
      "cover_url": "https://www.gutenberg.org/cache/epub/26301/pg26301.cover.medium.jpg",
      "downloads": 9815,
      "id": 26301,
      "release_date": null,
      "title": "Pride and Prejudice",
      "url": "https://www.gutenberg.org/ebooks/26301"
    },
    "… 9 more"
  ],
  "cached": false,
  "count": 11,
  "credits_used": 1,
  "next_page": null,
  "page": 1,
  "query": {
    "q": "pride and prejudice"
  },
  "sort": "downloads"
}

Response result

Response structure

Inferred from examples
  • books(object | string)[]
    • authorstring
    • cover_small_urlstring
    • cover_urlstring
    • downloadsinteger
    • idinteger
    • release_datenull
    • titlestring
    • urlstring
  • cachedboolean
  • countinteger
  • credits_usedinteger
  • next_pagenull
  • pageinteger
  • queryobject
    • qstring
  • sortstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Project Gutenberg book search API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.