FMCSA Carriers Scraper - USDOT, Legal Name, Fleet & Status avatar

FMCSA Carriers Scraper - USDOT, Legal Name, Fleet & Status

Pricing

from $1.80 / 1,000 results

Go to Apify Store
FMCSA Carriers Scraper - USDOT, Legal Name, Fleet & Status

FMCSA Carriers Scraper - USDOT, Legal Name, Fleet & Status

Search US motor carriers from the FMCSA MCMIS census open dataset (data.transportation.gov). Filter by name, USDOT, state or status. No API key.

Pricing

from $1.80 / 1,000 results

Rating

0.0

(0)

Developer

Brandt May

Brandt May

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

6 days ago

Last modified

Share

Carrier records for a focused search — illustrative workflow

Create a structured starting point for carrier research and fleet market mapping. This Actor reads the FMCSA MCMIS census open dataset, returning published identifiers, names, locations and fleet fields.

Open this Actor in Console · First run · Results · Cost · Full guide

Try this Actor

  1. Choose a small scope. Use the existing FEDEX legal-name sample and maximum of twenty-five carriers for an initial look. When switching to your own USDOT, state or status search, clear that prefilled name unless you want it to remain a filter.
  2. Run and review. Open the dataset's carrier table and the run's key-value-store SUMMARY for saved counts, source failures and incomplete runs.
  3. Use the results. Export CSV or JSON and retain the USDOT identifier when reconciling records with official sources.

Read this before using the data: These are census snapshot fields, not a live SAFER scrape or a determination of current operating authority, safety or insurance. Published phone fields are not enriched or contacted.

Result preview

The dataset view highlights these columns:

  • USDOT number · dotNumber
  • Legal name · legalName
  • Doing-business-as name · dbaName
  • MCMIS status code · statusCode
  • Physical city · phyCity
  • Physical state · phyState

Use the original source links and the field definitions below when interpreting the results. CSV works well for flat columns; JSON preserves nested values.

Usage and pricing

Base result rate on the FREE tier: $3 per 1,000 results. The Pricing tab shows your plan's result rate and any Actor Start charge. Set a small result limit for the first run; the requested limit is not a guarantee of that many results.


Full guide

Search US motor carriers from the FMCSA MCMIS census open dataset on data.transportation.gov. No API key.

What it does

Queries https://data.transportation.gov/resource/az4n-8mr2.json (Census of Active Motor Carriers) and returns USDOT, legal/DBA name, status, physical city/state, carrier operation, power units, drivers, and phone when published.

Who it's for

  • Freight brokers / shippers vetting carriers
  • Insurance and compliance teams doing USDOT lookups
  • Market mappers filtering by name or state

Input

  • nameContains — FEDEX sample only when no search filters are supplied
  • dotNumbers — optional exact USDOT list; name/state/status filters also apply
  • state / statusCode — optional filters (A=active, I=inactive)
  • maxResults / maxRunSeconds

Limitations

  • MCMIS census snapshot fields — not a live SAFER HTML scrape.
  • QCMobile developer webKey enrichment is intentionally omitted so defaults stay keyless.
  • Phone numbers are source fields only; no contact enrichment.

Result accounting

Only real source records are written to the dataset. SUMMARY.total counts saved rows. A dataset spending cap stops further writes and sets SUMMARY.stoppedOnChargeLimit and SUMMARY.incomplete. Source failures and time limits are reported in the summary; they do not generate substitute result rows.

Help with your run

Open the Issues tab on this Actor with the run URL, the input field that caused trouble and what you expected to receive. Remove API keys and private information before posting.

Explore more Mayd-It Actors

Understand your run

Open Run report in the run’s Output tab for saved-record counts, reported source issues and limits, and suggested next steps. Use CSV export to take the saved results into a spreadsheet. The existing JSON results and detailed machine-readable summary remain available.

The report reflects this run’s recorded coverage. A successful run or a saved result does not establish that every possible source record was collected.