Coverage and data sources
Where the data comes from and how to read the coverage envelope on every shipment query before drawing a conclusion.
Shipment queries return a coverage envelope alongside the rows. Read it before
drawing a conclusion — it is the difference between "there is no trade here" and
"we cannot see this lane".
The envelope
{
"coveredCountries": ["US", "CO"],
"periodStart": "2024-01",
"periodEnd": "2026-06",
"status": "covered",
"confidenceLevel": "high",
"completenessRatio": 0.91,
"usageGuidance": "…",
"blindSpot": "…"
}
Reading status
| Status | What you may conclude |
|---|---|
covered | Strong evidence — the query saw the lane properly |
partial | Directional only — trends are usable, absolutes are not |
limited | Directional only, and weakly so |
unavailable | Nothing usable for that query or period |
Where the data comes from
- Importer and exporter discovery data
- WTO and national tariff schedules
- The OFAC SDN sanctions list
- Per-shipment customs and bill-of-lading records
- Live company-website crawls
- People-search sources for contacts
Every row carries the source it came from, so a result can always be traced back rather than taken on trust.
Surfacing it honestly
When you report a finding, report its coverage with it. "Top five buyers in this
lane, from a partially covered feed" is a usable sentence. "Top five buyers in
this lane" alone, built on partial coverage, is one that will be wrong at the
worst possible moment.
Methodology and the published benchmark for the corpus are documented on the main site.