canonical: https://jentic.com/apis/archive.org/archive-search

# Archive Search Services

The Internet Archive Search Services API exposes the search infrastructure that powers archive.org's catalogue lookup over books, audio, video, software, and web archives. The API offers three endpoints: a metadata fields listing, an organic relevance-ranked search, and a high-throughput scrape endpoint for bulk export. It is intended for researchers, librarians, and tooling that needs structured access to the Internet Archive corpus rather than HTML scraping.

## For AI agents

Search the Internet Archive corpus by keyword and metadata, and bulk-export matching item records.

## Scope

Does not handle Wayback URL lookups, item upload, or full-text content download - use for catalogue-wide search and bulk export only.

## Capabilities

- Run a relevance-ranked organic search across the archive.org item corpus
- Bulk-export matching records via the scrape endpoint without pagination cliffs
- List the metadata fields available on archive.org items for query construction
- Filter searches by media type, collection, or creator using metadata field syntax
- Combine field listings with scrape calls to extract a complete metadata view

## Use cases

### Researcher Catalogue Search

Run keyword and metadata-filtered searches against the Internet Archive corpus to discover books, recordings, and films relevant to a research project. Academic and digital-humanities tooling uses this to surface primary sources without scraping the web UI. The /search/v1/organic endpoint returns relevance-ranked results with item identifiers and metadata.

Example prompt: Call GET /search/v1/organic with the user's keyword and a mediatype filter, then return the top 10 item identifiers and titles.

### Bulk Metadata Export

Export the complete set of items matching a query for offline indexing or research analytics. Data engineers use the scrape endpoint to avoid the deep-pagination penalty of the standard search and to retrieve large result sets reliably. /search/v1/scrape paginates with a cursor and returns metadata-rich records.

Example prompt: Page through GET /search/v1/scrape with a cursor until exhausted to export every item in a target collection to a local JSONL file.

### Field Discovery for Query Construction

Inspect the available metadata fields on archive.org items to build precise queries against the search and scrape endpoints. Tooling builders use this to construct dynamic query interfaces without hardcoding the field list. /search/v1/fields returns the supported field names and their indexing characteristics.

Example prompt: Call GET /search/v1/fields to fetch the supported field list, then construct a filtered query using the appropriate field names.

### AI Agent Archive Lookup via Jentic

A research agent that drafts citations or pulls primary sources can call the Internet Archive Search through Jentic to find materials by topic or author. The agent searches for the lookup operation, loads the schema, and executes without managing pagination boilerplate. Because this API is open, Jentic adds discovery and orchestration value rather than credential isolation.

Example prompt: Use Jentic search 'search the Internet Archive', load the schema for GET /search/v1/organic, then execute with the user's research keyword and return the matching item identifiers.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /search/v1/fields | List metadata fields available on items |
| GET | /search/v1/organic | Relevance-ranked organic search |
| GET | /search/v1/scrape | Cursor-based bulk export of matching items |

## Key resources

- **Fields** — List the metadata fields available on archive.org items for query construction
- **Organic Search** — Relevance-ranked search across the Internet Archive corpus
- **Scrape** — Cursor-based bulk export of items matching a query

## Why Jentic

- **Setup:** Wiring the Internet Archive Search Services by hand means learning its scrape and organic search parameters and paging its export responses yourself. These endpoints are open, so through Jentic you install once, import the Search Services from the API Directory, and your agent calls it without managing any credential.
- **Permission scoping:** The Search Services operations are open reads that carry their query in request parameters, so you limit the agent to the operations it needs, such as the fields, organic, or scrape search endpoints. You choose the operations it may call, so the agent only runs the read operations you have added.
- **Credential handling:** The Search Services endpoints are open, so there is no credential to store: your own Jentic One instance runs the operations without injecting any secret into the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'search the Internet Archive', and Jentic returns the matching Search Services operation with its input schema so the agent calls the right endpoint without browsing docs.

## Related APIs

- **Wayback Machine API** — Sister API on archive.org for looking up archived web snapshots by URL and timestamp.
- **ArchiveBox API** — Self-hosted web archiving system with its own search and snapshot store, contrasted with the Internet Archive's hosted corpus.
- **NASA APOD API** — Public open-data API often combined with archive.org searches in research and educational pipelines.

## FAQ

### What authentication does the Internet Archive Search API use?

The Search Services endpoints are open and do not require authentication for normal query use. Heavier or write-side archive.org operations require S3-style credentials, but the search and scrape endpoints documented here can be called anonymously.

### Can I bulk-export every item in a collection?

Yes. Use GET /search/v1/scrape with a query that filters by collection and page through the results using the returned cursor. The scrape endpoint is designed for full-corpus iteration and avoids the deep-pagination limits of organic search.

### What is the difference between /search/v1/organic and /search/v1/scrape?

Organic returns relevance-ranked results suitable for end-user search UIs and is limited to a few thousand records deep. Scrape returns records in a stable order with cursor pagination and is the right choice for bulk export of large result sets.

### What are the rate limits for the Search API?

The Internet Archive applies fair-use throttling but does not publish a fixed quota in the OpenAPI spec. Sustained high-frequency requests may be rate-limited; for heavy bulk export, prefer the scrape endpoint which is built for that pattern.

### How do I list the searchable metadata fields?

Call GET /search/v1/fields. The endpoint returns the list of field names that can be used in organic and scrape queries, including their indexed and stored characteristics.

### How do I search the Internet Archive through Jentic?

Install Jentic with pip install jentic, search for 'search the Internet Archive', load the schema for GET /search/v1/organic, then execute with your keyword. Jentic returns the matching items without you needing to wire pagination by hand.

### Can I limit what my agent is allowed to do with the Internet Archive Search API?

Yes. Because you run Jentic One yourself, your own rules decide which Internet Archive Search operations the agent may call, so you can add only the read endpoints it needs, such as GET /search/v1/fields, GET /search/v1/organic, or GET /search/v1/scrape. If a research agent should only look items up, you can add the organic search operation and leave the bulk scrape export out, and the agent can only run the operations you have added. These endpoints are open reads that carry their query in request parameters, so scoping the operation list is what controls what the agent can do.