DATA SHEET — FreightProof + Proof of Good Care

Rootz Corp · freight.rootz.global Carrier vetting + lifecycle proof-of-care for dispatchers, carriers, and warehouses

What it does

CapabilityDetail
Carrier vettingLive FMCSA lookup + risk score (0–100) mapped to the factors the Montgomery Court named. APPROVE / CAUTION / REJECT, with red-flag list.
Signed vetting recordSHA-256 snapshot of exactly what the data showed, when — answers "what did the dispatcher know, and when?"
Proof of Good Care documentHash-chained custody ledger that travels with the load: selection → tender → pickup → transit → warehouse in/out → delivery.
Care ScoreOne number, 0–100 (Grade A–F), per shipment — readable at a glance by an insurer, broker, court, or AI.
Independent verificationAnyone re-runs SHA-256 to confirm the document is unaltered. No Rootz account, no API key, no trust in us required.
Tamper-evidenceChanging any field after the fact breaks the chain and is pinpointed to the exact event.
Field capture (PWA)Mobile app for drivers / dock staff: photos, seals, temps, VIN scan, voice notes, inspections — offline-first, syncs when connected.
AI-native accessMCP server (12 tools) + REST API + .well-known/ai — any AI agent or TMS can vet a carrier or read a care document in seconds.
Anchoring (optional)Chain root anchored to Polygon for court-grade immutability.

The data behind it

Source (US DOT / FMCSA, public)Records
Carrier census4.4M carriers
Crash file3.6M crashes
Inspection / violation file4.85M inspections
Total loaded~12.8M government safety records
BASIC scores (live QCMobile API)on-demand per carrier
Enforcement / OOS / compliance reviewsschema ready; bulk ingest pending source access

Cross-referenced against 4.2M state business registrations (officer / EIN / shell-carrier detection).

Who it's for — and it covers all three at once

  • Dispatchers / brokers — discharge the Montgomery duty of care in carrier selection (49 U.S.C. §14501(c)(2)(A) safety exception).
  • Asset-based carriers (run your own trucks) — discharge the Carmack Amendment duty (49 U.S.C. §14706): prove condition at tender and delivery, unbroken custody.
  • Warehouses / 3PL (e.g. Warehowz) — discharge the UCC §7-204 bailment duty: condition in/out, storage conditions.

    • A company that does more than one of these (PAID/ShipTime does all three) gets a single document that defends every role.

    Legal basis

  • Montgomery v. Caribe Transport II, LLC, 608 U.S. ___ (2026) — 9-0, Barrett. Brokers owe ordinary care in carrier selection; FMCSA data = constructive knowledge; "the absence of a documented vetting process is itself evidence of negligence."
  • Carmack Amendment, 49 U.S.C. §14706 — carrier liability for cargo; condition at origin + destination is the prima facie case.
  • UCC Article 7, §7-204 — warehouse liability for failure of reasonable care.

    • Evidence you own — confidential by default, shareable on demand

    Proof of Good Care creates evidence, but evidence the party who made it owns and controls — not a record handed to a platform, a regulator, or a counterparty.

  • Confidential by default. A care document is private to its owner (encrypted to the owner's keys). It is not published, indexed, or shared — it sits sealed until there is a reason to produce it.
  • Shareable on demand. When you need it — an insurance claim, a cargo dispute, a Montgomery defense, an audit, a partner request — you disclose it selectively, to one party, and they can verify it independently (SHA-256) without trusting you, or you them.
  • You control the timing, never the content. Because it is tamper-evident, you choose when to reveal it but never what it says — which is exactly what makes self-produced evidence credible to a court or an underwriter.

    • Net posture: confidential the rest of the time, provable the moment you need it. Your proof becomes an asset you hold — not a liability someone else holds over you.

    How it plugs in

    `` ShipTime label/dispatch → seeds the document (vetting + QR on the label) Driver / dock (PWA) → appends tender, pickup, delivery handoffs Warehowz intake/outtake → appends warehouse-in / warehouse-out → Care Score + chain root, verifiable at /care/{id} ``

    Smallest first: a one API call at label time turns every ShipTime label into a defensible dispatch receipt — sellable on day one, before the rest is wired.

    Status (Jun 2026)

    Vetting engine live. Proof-of-Care document engine + web/JSON routes + verification live in production (freight.rootz.global). Next: ShipTime label-time hook → Warehowz custody events → live sensor feeds.

    Data from FMCSA (public, free). Proof from Rootz (hashed, attested, yours).