Wayback Machine captures of a URL API

Use the Wayback Machine captures of a URL API to retrieve capture listings, timestamps, status codes and archived URL references. Search captures for an exact URL, prefix, host or domain, narrowing date, status and MIME filters and optional de-duplication; use the returned cursor to browse further capture metadata. Verify that a historical capture exists, compare capture dates, or retain an archive link for a dated source reference. An archive capture represents a historical observation, not a guarantee that the original page is still available today. The detail page provides request and response examples, supported parameters, and usage pricing.

Selected price
$0.002 / billing creditPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters
A page link or a domain, with or without https://.
Optional parameters (14)
From date: YYYY, YYYYMM, YYYYMMDD or YYYYMMDDhhmmss (dashes allowed).
To date, same forms.
exact (default), prefix, host or domain.
HTTP status filter: 200, 3xx, !404.
MIME type filter: text/html, application/pdf, image/*.
One capture per hour, day, month, year, content or url.
oldest (default) or newest.
Captures per page, up to 1000 (default 100).
next_cursor from the previous page.
0 leaves out the bulky `raw` source blocks (often 10-30x smaller).
Comma-separated fields to return, e.g. `posts.id,posts.title`. Call metadata is always included.
1 skips the 24-hour cache and fetches live.
JSON only for this OpenAny product. Omit output or use json; CSV and NDJSON exports are not exposed.
Native CSV/NDJSON record selector; it has no effect on this JSON-only product.

Sample response

{
  "applied_filters": {},
  "cached": false,
  "count": 100,
  "credits_used": 1,
  "limit": 100,
  "next_cursor": "eJxLzs_VSa1IzC3ISdXUVzAyMDAxMDMyMzQ0MDI1AgB_dgeP",
  "snapshots": [
    {
      "date": "2002-01-20T14:25:10Z",
      "digest": "HT2DYGA5UKZCPBSFVCV3JOBXGW2G5UUA",
      "id": "20020120142510/http://example.com:80/",
      "length": 1792,
      "mime": "text/html",
      "raw_url": "https://web.archive.org/web/20020120142510id_/http://example.com:80/",
      "snapshot_url": "https://web.archive.org/web/20020120142510/http://example.com:80/",
      "status": 200,
      "timestamp": "20020120142510",
      "url": "http://example.com:80/",
      "urlkey": "com,example)/"
    },
    {
      "date": "2002-03-28T01:28:21Z",
      "digest": "UY3I2DT2AMWAY6DECFCFYMT5ZOTFHUCH",
      "id": "20020328012821/http://www.example.com:80/",
      "length": 481,
      "mime": "text/html",
      "raw_url": "https://web.archive.org/web/20020328012821id_/http://www.example.com:80/",
      "snapshot_url": "https://web.archive.org/web/20020328012821/http://www.example.com:80/",
      "status": 200,
      "timestamp": "20020328012821",
      "url": "http://www.example.com:80/",
      "urlkey": "com,example)/"
    },
    "… 98 more"
  ],
  "url": "example.com"
}

Response result

Response structure

Inferred from examples
  • applied_filtersobject
  • cachedboolean
  • countinteger
  • credits_usedinteger
  • limitinteger
  • next_cursorstring
  • snapshots(object | string)[]
    • datestring
    • digeststring
    • idstring
    • lengthinteger
    • mimestring
    • raw_urlstring
    • snapshot_urlstring
    • statusinteger
    • timestampstring
    • urlstring
    • urlkeystring
  • urlstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Wayback Machine captures of a URL API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.