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.
3 endpointsThe Internet Archive Wayback Machine API exposes the canonical lookup that determines whether a given URL has an archived snapshot and, if so, returns the closest available capture. The API offers two endpoints — a GET and a POST variant of the availability lookup — so callers can either pass the URL as a query parameter or send a batched request body. It is the same backbone that powers archive.org/wayback/available and is widely used in citation tooling, dead-link recovery, and journalism workflows.
2 endpointsStep 1: 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 | shStep 2: 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 instanceJentic 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.