web capture record

One row in a web-archive index describing a single crawl of a URL at a timestamp, carrying the urlkey, capture timestamp, mimetype, statuscode, digest and length, aggregatable by host, domain, path prefix or mimetype.

In this catalog it appears concretely: - Wayback Machine CDX Server API — "One record per capture of a specific URL at a specific timestamp; aggregatable by host, domain, path prefix or mimetype".

A label on a listing is not a deliverable. Teams that license on the strength of a product-name match routinely find the shipped files cover a narrower slice than they assumed, and backfilling history afterwards costs more than the license ever did.

The failure mode is concrete: a source can carry the web capture record label while differing from what you need on exactly the dimension that matters — One record per capture of a specific URL at a specific timestamp; aggregatable by host, domain, path prefix or mimetype. Comparing two sources on that line usually settles the choice faster than any feature matrix.

You rarely have to take a vendor's word for it. 82.4% of the 1,744 datasets Datadory catalogs are free to access, and Wayback Machine CDX Server API lets you inspect the real artifact before any budget is committed.

Treat every claim of this attribute as testable:

1. Open Wayback Machine CDX Server API and confirm its record — "One record per capture of a specific URL at a specific timestamp; aggregatable by host, domain, path prefix or mimetype" — against the files you actually receive.
2. Pin down update cadence in writing. Across this catalog, 22.6% of 1,744 datasets refresh daily and 64 still arrive only through a manual request form, so ask exactly how fresh each release is.
3. Check whether definitions are verified at all. Field definitions are verified for 1495 of 1,744 datasets (85.7%), and any source you license should meet that bar.
4. Price the delivery route before the license. In this catalog bulk download is the most common access method (725 datasets) ahead of official APIs (574), and 379 sources still require scraping — a maintenance cost that lands on you, not the vendor.

See the term applied to real records: interactive-media-services data.

Adjacent concepts worth reading next: - domain popularity ranking - hourly pageview files