Search Services

Name: Search Services API
Brand: Search Services
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsMonitoring Observabilitynone3 EndpointsREST

For Agents

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

Connect the Search Services to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Search Services, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

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

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 Search Services API.

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

GET STARTED

Start building with Search Services API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Search Services API for, with concrete tasks.

★ 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.

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.

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.

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.

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

3 endpoints — the internet archive search services api exposes the search infrastructure that powers archive.

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

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

Why though Jentic?

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

Credential isolation

The Search Services endpoints are open, so Jentic does not need to inject credentials. Jentic adds value by exposing the operations through intent search rather than by isolating secrets.

Intent-based discovery

Agents search by intent (e.g. 'search the Internet Archive') and Jentic returns matching Search Services operations with their input schemas, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct integration: a few hours to handle organic vs scrape pagination and the field syntax. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Wayback Machine API

Sister API on archive.org for looking up archived web snapshots by URL and timestamp.

Use Wayback when the workflow needs an archived snapshot of a specific URL; use Search when the workflow needs catalogue-wide discovery.

Alternative

ArchiveBox API

Self-hosted web archiving system with its own search and snapshot store, contrasted with the Internet Archive's hosted corpus.

Choose ArchiveBox when the workflow needs a private archive under your control; pick archive.org Search for the public Internet Archive corpus.

Complementary

NASA APOD API

Public open-data API often combined with archive.org searches in research and educational pipelines.

Pair with archive.org Search when an educational or research workflow draws from multiple open-data sources.

FAQs

Specific to using Search Services API through Jentic.

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.