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

# Internet Archive APIs

Internet Archive is a nonprofit digital library that preserves books, audio, video, software, and archived web pages. Its APIs give programmatic access to two parts of that mission: searching and bulk-exporting the item corpus, and looking up archived snapshots of web pages in the Wayback Machine. Both APIs are open reads over public data, so they are commonly used in research, digital-humanities, journalism, and citation tooling that needs structured access rather than HTML scraping.

## For AI agents

An agent can search and bulk-export the Internet Archive item corpus by keyword and metadata, and check whether any URL has an archived Wayback Machine snapshot to recover the closest capture for citations or dead-link repair.

## Scope

Use for: Searching and bulk-exporting the Internet Archive item corpus and looking up archived Wayback Machine snapshots of specific URLs

Not supported:
- page archiving submission
- item upload
- full-text download
- user authentication

## APIs

| API | Category | Endpoints | Description |
| --- | --- | --- | --- |
| Search Services | developer-tools | 3 | Search the Internet Archive corpus by keyword and metadata, and bulk-export matching item records. |
| Wayback API | developer-tools | 2 | Look up whether the Wayback Machine has an archived snapshot of a URL and return the closest capture timestamp. |

## Which API to use

| Need | API | Why |
| --- | --- | --- |
| Find or bulk-export archived items by keyword, collection, or creator | search | Search Services queries the archive.org item corpus and exports matching records via a cursor-based scrape endpoint. |
| Check whether a specific web URL has an archived snapshot | wayback | The Wayback API returns the closest archived capture and timestamp for a given URL, which item search does not cover. |

## Cross-API use cases

### Discover then verify archived sources

A research agent searches the Internet Archive corpus for materials on a topic, then confirms that the web sources it cites still have archived snapshots so the citations stay stable. Search Services surfaces the items and the Wayback API checks that referenced URLs are captured.

Example prompt: Call the search API to find items matching a research keyword, then for each external source URL call the wayback API to return the closest archived snapshot and timestamp.

### Curated link list with archival backup

A curation tool builds a topic reading list from the Internet Archive corpus and ensures every external link in it already has a Wayback snapshot before publishing, so readers can fall back to the archived version if a source goes offline.

Example prompt: Use the search API to assemble candidate items for a topic, then batch-check their source URLs with the wayback POST availability lookup and flag any that are not yet archived.

## Why Jentic

- **Setup:** Both Internet Archive APIs are open, so through Jentic you install once and add the Search Services and Wayback operations from the Jentic directory, and your agent calls either one without wiring pagination or handling both GET and POST variants by hand.
- **Permission scoping:** These are open read operations that carry their query or URL in request parameters, so your own rules decide which ones the agent may call. You can add only the lookups a workflow needs, such as organic search or Wayback availability, and leave bulk scrape export out.
- **Credential handling:** There is no credential to store for either API, so 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 searching the Internet Archive or finding an archived snapshot of a URL, and Jentic returns the matching operation with its input schema across both APIs so the agent picks the right endpoint.

## Related vendors

- **ArchiveBox** — Self-hosted web archiving system with its own snapshot store, an alternative when you need a private archive under your control.
- **NASA** — Public open-data APIs frequently combined with Internet Archive lookups in research and educational pipelines.
- **Library of Congress** — Another large public digital library whose collections research tools often query alongside the Internet Archive.

## FAQ

### Do the Internet Archive APIs require authentication?

No. Both the Search Services and Wayback APIs are open reads over public data and can be called anonymously. Heavier write-side archive.org operations such as uploads use separate S3-style credentials, but the search, scrape, and availability endpoints covered here do not.

### When should I use Search Services versus the Wayback API?

Use Search Services when you need catalogue-wide discovery or bulk export of archived items such as books, audio, video, and software. Use the Wayback API when you already have a specific web URL and need to know whether it has an archived snapshot and what the closest capture is.

### Can I combine both APIs in one workflow?

Yes. A common pattern is to discover source material with Search Services and then use the Wayback API to confirm that referenced web pages are archived, which keeps research citations and curated link lists stable over time.

### Are these APIs suitable for bulk work?

Yes, within fair-use limits. Search Services offers a cursor-based scrape endpoint built for full-result-set export, and the Wayback API accepts a batch of URLs in a single POST availability request. The Internet Archive applies fair-use throttling rather than a published fixed quota.

### Can these APIs add or upload content to the Internet Archive?

No. Both APIs are read-only lookups. They do not submit pages to be archived, upload items, or download full-text content. Saving a new page uses the separate Save Page Now interface, and uploads use the write-side archive.org operations.

### How does an agent decide which Internet Archive operation to call?

The agent searches Jentic by intent, such as searching the Internet Archive or finding an archived snapshot of a URL, and Jentic returns the matching operation with its input schema. The agent then calls the right endpoint without browsing the docs.