# Wayback URL History (`visioweb/wayback-url-history`) Actor

- **URL**: https://apify.com/visioweb/wayback-url-history.md
- **Developed by:** [Francesco Ingrosso](https://apify.com/visioweb) (community)
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 url checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Wayback URL History

Check **how long a web page has existed and how often it was archived**, using the Internet Archive CDX API (official, no key).

### Input

```json
{ "urls": ["example.com", "apify.com/store"], "matchType": "exact", "maxSnapshots": 5, "maxConcurrency": 2 }
```

`matchType`: `exact` (this URL only), `prefix` (anything starting with it), `domain` (whole domain), `host`.

### Output

One item per URL: `snapshotCountReturned`, `firstSnapshot` and `lastSnapshot` (timestamps `YYYYMMDDhhmmss`), `archivedYears`, and `snapshots` (timestamp, status code, mime type).
If the page was never archived: `status: "ok"` with `snapshotCountReturned: 0` and a note (still charged: the answer "never archived" is the result).

### Statuses

`ok`, `rate_limited` (free), `error` (free).

### Pricing

Charged once per URL checked (`url-checked`).

### Notes

The archive is slow and rate-limits: 1.5 s between requests, max 4 in parallel. A busy archive answers 429; retry later.

# Actor input Schema

## `urls` (type: `array`):

URLs or domains to look up in the Internet Archive.

## `matchType` (type: `string`):

exact = this URL only; prefix = URLs starting with it; host = the whole host; domain = host and subdomains.

## `maxSnapshots` (type: `integer`):

Maximum number of snapshots returned for each URL (1 to 100).

## `maxConcurrency` (type: `integer`):

How many URLs are processed at the same time (1 to 4). Requests to the Archive are spaced out.

## Actor input object example

```json
{
  "urls": [
    "example.com"
  ],
  "matchType": "exact",
  "maxSnapshots": 5,
  "maxConcurrency": 2
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "urls": [
        "example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("visioweb/wayback-url-history").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "urls": ["example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("visioweb/wayback-url-history").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "urls": [
    "example.com"
  ]
}' |
apify call visioweb/wayback-url-history --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,visioweb/wayback-url-history"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/XKTfQzUa2CWA1blaJ/builds/wM5WkhWVRfnPY4fUh/openapi.json
