- Type
- not stated
- Format
- Multimodal delivered through four surfaces: a Logistics Data API (JSON for software/AI systems), reports, an account console with usage metering, and map layers — with source and date metadata carried on each field
- Volume
- Narrow but deep: 4 border solutions live now with Laredo production-ready and one named crossing's lane-level wait series plus weather/road overlays; volume per crossing is high-frequency time series (lane-level wait states sampled continuously across every lane and bridge of a commercial port), so a single busy crossing generates hundreds of thousands of timestamped observations per year. Coverage breadth is deliberately limited (Laredo ready; Otay Mesa and Detroit/Windsor only on request).
- Users
- N/A — usage-metered B2B data subscription with an account console for named customer seats; no consumer registration base is published (early-stage vendor, pricing stated per-call at $0.0059 rather than per-user)
- History
- not stated
- Update frequency
- not stated
- Growth
- Active but pre-scale — a live, purchasable product (usage pricing published, account console and API shipping) whose flagship relationship is still being wired: the site states the commercial contract for the featured product story is ready while 'the dedicated production connection is still pending', and two of three named crossings are roadmap rather than delivered.
- Launched
- ~2025-2026 (no launch date printed; bounded by a provider organisation record created in 2026 and by a site that is explicitly launch-stage — 'Start with Laredo', coverage requested on a per-crossing basis)
- Delivery
- not stated
- Entity mapping
- not stated
- Sample
- not stated
- Point-in-time
- not stated
- Licence
- not stated