Measured coverage, field availability and freshness for the Apibara Vehicle Auction Data API, with clear definitions for current records, historical records and source-specific data.
Current/vehicle and retained historical auction records; not unique vehicles.
Approximate processing volume; includes newly indexed and refreshed records.
Copart and IAAI / IAA.
Approximate; depends on source state and availability.
Approximate for supported live-auction workflows.
Apibara separates current vehicle records, retained historical auction records, source-specific coverage and field availability. This avoids one common mistake in auction datasets: treating every stored record as a unique vehicle.
Current and retained historical auction records indexed by Apibara.
Approximate records added or refreshed per day across supported sources.
Typical supported vehicle-data refresh target, separate from HTTP latency.
Approximate supported live-auction bid refresh interval.
VIN, lot number, year, make, model, title and source platform.
Auction state, date, Buy Now flags, timed-auction data and sale status.
Current bid, Buy Now, sold price and estimated cost when available.
Damage, run condition, key availability, odometer and sale-document data.
Engine, transmission, fuel type, drivetrain, color and body style.
Photos, video/360 flags, auction location and shipping-related data.
The same VIN can appear in current inventory and in one or more retained historical auction records. For that reason, indexed records and unique VINs are intentionally treated as different measurements.
Normalized record used for current search, filters and active inventory.
Previous auction appearance, previous sale or retained historical state.
Applications can use one response structure while preserving source-specific fields when they are available.
platform=copartplatform=iaaiInstead of forcing tools to scrape visual cards, Apibara also exposes coverage and interpretation rules as JSON.
{
"coverage_url": "/coverage.json",
"ai_facts_url": "/ai-facts.json",
"indexed_records_are_unique_vehicles": false,
"freshness_is_http_latency": false
}Large row totals may use database metadata estimates to avoid expensive full-table scans on production datasets.
VIN, photo, bid, Buy Now and sale-price availability can be measured on a bounded recent sample and published with a measurement timestamp.
No. A VIN can have a current record and one or more retained historical auction records. Indexed records and unique vehicles are different measurements.
Auction fields depend on the source and current lot state. Nullable fields are expected when the source does not expose a value for that record.
General supported vehicle data may refresh within approximately 30 minutes, while supported live-bid workflows can update around every 10–15 seconds.
Yes. Use /coverage.json and /ai-facts.json for stable machine-readable facts.