Every FMCSA carrier, and everything your team knows about them, in one record.
Trucking company data on every registered carrier and broker: contacts, authority, insurance, fleet, and safety in one consolidated record, updated every day. Work it in the platform, pull it by API, or take delivery of the whole file.
14 days free on Pro · card required · cancel anytime
Trucking company data is the record every interstate carrier and broker files with FMCSA, scattered across separate systems. CarrierOk reconciles those sources into one record per company, adds the scoring FMCSA does not publish, and delivers it three ways: worked in the app, pulled by API, or taken as a file.
- What is in the record
- Legal and DBA name, contacts, operating authority with revocation history, insurance filings, fleet and equipment decoded from VINs, inspections, crashes and safety scores.
- Who it covers
- Every FMCSA registrant, including brokers and freight forwarders, and inactive records as well as active ones, so authority history is searchable rather than only today's snapshot.
- How current
- Sources are re-ingested when they publish rather than on a fixed clock, so the record updates throughout the day and monitoring reports a change the same day.
- Three ways to take it
- Work it in the platform with lists, tags and notes; pull it per carrier through the REST API; or take delivery of the whole file to your own cloud storage.
- Why buying a list ages badly
- A purchased list is a copy that starts drifting the day it lands. The same filters rebuilt here return today's answer, and your own tags and notes stay attached to the live record.
The data prep is already done.
Trucking company data is published across six FMCSA systems with different keys, formats, and schedules. CarrierOk is the data engineering team that reconciles them: aggregation, cleanup, and every exception are our job, so what lands in your bucket is ready to load whether you have a data team or not.
Fresh enough to be first
CarrierOk watches FMCSA sources as they publish, throughout the day. A carrier that registers today is in tomorrow's file.
A schema that holds still
The same structure, delivery after delivery, so your pipelines and models never miss a beat. Field-level documentation ships with every dataset.
Every exception, already handled
Duplicates, malformed filings, and conflicting records are reconciled before delivery. The cleanup lives on our side, permanently.
Every FMCSA system, one file
Census, authority, insurance filings, inspections, and crash records arrive joined per carrier in one consolidated schema instead of six raw downloads.
Contacts come with the record, not as a separate charge.
Every record carries the primary contact, phone, cell, email, and website the carrier filed, alongside authority, insurance, fleet, and safety. One record per carrier, not a contact file you have to match back.
- Legal name
- DBA
- USDOT #
- MC / docket #
- EIN
- Entity type
- Primary contact
- Phone
- Cell
- Website
- Physical address
- Mailing address
- Status
- Grant date
- Common
- Contract
- Broker
- Out-of-service date
- Insurance carrier
- BIPD on file
- Cargo
- Bond
- Coverage amounts
- Cancellation date
- Power units
- Trucks
- Tractors
- Trailers
- Drivers
- CDL drivers
- Annual mileage
- Inspections
- Vehicle OOS rate
- Driver OOS rate
- Crashes
- Safety rating
- Cargo carried
Coverage follows what each carrier filed with the FMCSA, so some records are missing a field. The bulk file carries 200+ of these fields per carrier; BASIC percentiles, ISS, risk signals, and VIN-decoded equipment are derived intelligence and live in the API and the platform.
Your carrier pipeline, on data that updates itself.
Data bought as a file has to be imported before anyone can work it, and from then on your team maintains a copy that no longer matches the source. In CarrierOk the record updates itself and your work sits on top of it: who is on which list, what you said to them, where they sit, and when you last spoke.
Lists, tags, and a stage per list
Group carriers your way, label them in your own words, and track where each one sits in your process. Lists are yours by default; what your team writes down is visible to the team.
Notes and an activity timeline
Every note, call, and export is recorded against the carrier, so the next person to open the record can see what already happened and who it happened with.
Saved views that count what changed
Save a search and the app tells you how many new carriers have matched it since you last looked. Carriers that register this week show up in the view you built last month.
Bring the book you already have
Import a CSV of DOT, MC, or EIN numbers and the app matches them to the record. Anything that could not be matched comes back by value, with the reason, so nothing goes quietly missing.
Your lists, tags, and stages come out in the export
An export carries the record’s columns and yours in the same file, so the work your team did in the app is portable the day you want it somewhere else.
A purchased list decays. This record updates every day.
CarrierOk measured every carrier that held authority and insurance in May 2025, all 351,429 of them, and followed them for twelve months.
Authority goes away
Of the carriers holding authority and insurance at the start of the window, 18.2% had that authority revoked inside twelve months.
Insurance lapses quietly
25.7% had a BIPD policy cancelled and nothing new on file thirty days later. No notice reaches a file you already downloaded.
And it starts immediately
9.9% were revoked or lapsed inside the first ninety days. A list bought in January is wrong by spring.
FMCSA licensing and insurance history in the CarrierOk warehouse, measured August 24, 2026. Aggregates only.
Delivered how you want it: platform, API, or bulk file.
The same consolidated record, delivered where your team works. Most start in the platform and add a feed once they know which fields they need.
Platform
For teams who want to work carriers, not warehouse them.
Search and filter the whole record in the app, then keep your lists, tags, notes, and stages on it. Exports carry your columns back out.
Priced per month, per plan. Free trial.
See the platform →API
For engineers putting carrier data inside their own product.
One call returns the consolidated profile. This is also where CarrierOk's derived intelligence lives: all 7 BASIC percentiles, ISS with its FMCSA recommendation, and 50+ risk signals.
Priced per endpoint on the developer portal.
See the API →Bulk data
For data teams loading the whole universe into a warehouse.
Every FMCSA-registered carrier and broker as compressed CSV, under a dated prefix in a bucket you own, every day. 200+ fields, and no derived intelligence in the file.
Quoted against the use case. Starts with a sample file.
Request sample data →Winning sales pipelines, underwriting models, and software products run on this record.
A pipeline, a model, or a product built on carrier data cannot afford to be wrong. Keeping the record accurate, current every day, and dependable is our full-time job.
The foundation under your outbound.
Segment the universe with your own filters, work the results as lists, and reach carriers in the week they first appear.
Underwrite from the record, not the application.
Authority status and insurance filings for every carrier, current each morning and structured for your models.
Underwriting use case →Power your product with the dataset.
Build the CRM, search, or marketplace on resident data that refreshes with every daily drop.
Platform integration →Trucking Company Data FAQ
Start with a free trial, or a sample file.
Open the directory today, or ask the data team for a sample file and field-level documentation before you buy a feed.