Skip to main content
BrokerDefender
Data accuracy

Where BrokerDefender's data comes from, and what we do with it.

BrokerDefender does not maintain an independent carrier database. Every data point shown in a vetting record is sourced from the Federal Motor Carrier Safety Administration. This page describes the source, what BrokerDefender does and does not do to the data, and the limits of what an FMCSA-derived record can prove.

Source

All carrier data is retrieved live from the FMCSA QCMobile API at https://mobile.fmcsa.dot.gov/qc/services/. QCMobile is the agency's official machine-readable interface for carrier records and is the same source SAFER, the QCMobile mobile app, and the FMCSA's own portal use. BrokerDefender authenticates via an FMCSA-issued webkey obtained through Login.gov.

What we retrieve

For each USDOT number, BrokerDefender retrieves the carrier's registration record, operating authority status, safety rating, roadside-inspection statistics, crash history, BIPD insurance filings (when present), and out-of-service rates. The full response payload is stored unmodified before any decision logic runs.

What we do not do

  • We do not modify the underlying data. The raw/carrier_snapshot.json file inside every Due Diligence Packet is the verbatim FMCSA payload as received, byte-for-byte.
  • We do not supplement with third-party data. No insurance verification services, no broker-credit databases, no "carrier vetting" aggregators feed into the determination. The only inputs are FMCSA and the load type the broker selects.
  • We do not exclude carriers. BrokerDefender returns data for every FMCSA-registered entity, including brand-new authorities, intrastate-only carriers, recently revoked authorities, and private (non-for-hire) carriers. Some platforms exclude these; the carriers most likely to expose a broker to liability are often exactly the ones excluded elsewhere.
  • We do not independently verify FMCSA's data. FMCSA records reflect what carriers have filed and what inspectors have recorded. BrokerDefender presents that data; it does not warrant it.

Known limits of FMCSA data

FMCSA's records are the best available federal source on motor carriers, but they have known limitations a careful broker should understand:

  • Insurance is reflective, not authoritative. The "on file" liability amount reflects FMCSA's most recent filing from the carrier's insurer. It is not real-time confirmation that the policy is currently in force. A carrier may have a lapsed policy that has not yet been removed from the FMCSA record, or a renewed policy that has not yet been filed. Always confirm coverage directly with the carrier's broker before tendering a load.
  • Inspection and crash data lags. Roadside inspections are recorded by state enforcement agencies and forwarded to FMCSA on varying schedules. A carrier's record may not reflect inspections or crashes from the last 30-60 days.
  • MCS-150 currency is self-reported. Carriers are required to refile MCS-150 every two years. FMCSA flags overdue filings but cannot verify the accuracy of what was filed.
  • Safety ratings are issued, not continuous. A "Satisfactory" rating reflects the carrier's status at the time of the most recent compliance review. Many smaller carriers operate without a current rating because FMCSA has not reviewed them recently. "Not rated" does not mean "unsafe"; it means "no determination has been made."
  • Intrastate carriers are visible but limited. Some intrastate-only carriers maintain less complete FMCSA records because federal reporting obligations differ from interstate-authority carriers.

Snapshot integrity

Each Due Diligence Packet includes the SHA-256 hash of the FMCSA snapshot file inside the packet. The hash is computed at packet generation and printed in the Forensic Audit Record alongside the hashes of every PDF. To confirm the snapshot has not been altered after generation, recompute the SHA-256 of raw/carrier_snapshot.json and compare against the printed value.

Reporting an error

If a vetting record shows data you believe is wrong, the first place to check is the FMCSA record itself at mobile.fmcsa.dot.gov/qc. If the FMCSA record itself is wrong, the carrier is responsible for filing the correction with FMCSA. BrokerDefender cannot alter FMCSA data. If BrokerDefender appears to be misreading correct FMCSA data, contact us and we will investigate.