FMCSA Motor Carrier Leads 🚛

foXLabs US lead series: USPTO trademarks · Insurance producers · Employer benefit plans · Federal contractors

🎉 Turn the FMCSA registry into clean, structured carrier-lead data — no login, no API key, one row per carrier, with DOT/MC numbers, fleet size, operation, contact and status. Built for insurance, factoring and logistics sales.

🔍 What is the FMCSA Motor Carrier Leads — and when should you use it?

Pick a lead mode — carriers whose operating authority was just granted, brand-new USDOT registrations, or a filtered search of all active carriers — and this Actor returns the matching carriers from FMCSA's official open data as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run reads the source live. There is no lookup by carrier name or DOT number: you select by date, state, cargo, fleet size and operation.

Use it when you need: fresh trucking leads for factoring, insurance, fuel-card, ELD or equipment sales; a list of active carriers in a state, cargo type or fleet-size band; or a daily feed of new authorities.

Use something else when: you need financials — the FMCSA registry is operating authority and safety data, not company financials.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/fmcsa-carrier-leads.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull carrier company records using the Apify Actor `foxlabs/fmcsa-carrier-leads`.
Input: `mode`, `authorityEvents`, `datePreset`, `dateFrom` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"mode":"new_authorities","maxResults":1000}
Ask me what to look up, run the Actor, then summarise the rows as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/fmcsa-carrier-leads.md.

📋 Overview

Everything you need to turn the FMCSA motor-carrier registry (official open data) into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Three lead modes — newly granted authorities, new USDOT registrations, or a filtered search of the active-carrier census.
• 🧹 No empty-promise columns — only fields this registry actually fills; degenerate columns are removed.
• 🔗 Stable identifiers — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
• 💰 Per-row pricing — a minimal price per delivered row, no subscription.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🚚 Lead modes — new_authorities (authority just granted, joined with the carrier's contact record), new_registrations (new USDOT numbers) and search (active carriers by filter).
• 🎯 Filters — state (2-letter code or full name), cargo type, fleet size, interstate / intrastate operation, phone or email required, date range.
• 🏢 Carrier profile — USDOT number, legal name, phone, email, officers, physical and mailing address, power units, drivers, cargo types, registration date and, for new authorities, the docket number and grant date.
• ⚡ Runs that end on their own — rows are delivered in batches; a run stops cleanly when maxResults, your maximum charge or the run timeout is reached, and its status message says which.
• 🧹 Clean schema — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~fmcsa-carrier-leads/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"new_authorities","maxResults":1000}'

🚀 Getting Started (3 steps)

1. Choose a lead mode and filters — new authorities, new registrations or search; then states, cargo, fleet size.
2. Set the cap — maxResults limits how many results are returned.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"mode":"new_authorities","maxResults":1000}

Field	Type	Description
mode	string	New authorities = carriers whose operating authority was just GRANTED (the classic factoring/insurance lead feed, joined with full contact data). New…
authorityEvents	array	Which authority events count as a lead (new-authorities mode). Default: freshly GRANTED authorities only. Reinstated = carriers whose authority just came back…
datePreset	string	For 'new authorities' this filters the authority grant date; for 'new registrations' the USDOT creation date; for 'search' it optionally limits by registration…
dateFrom	string	YYYY-MM-DD (e.g. 2026-07-01). Only used when Date range = Custom.
dateTo	string	YYYY-MM-DD. Only used when Date range = Custom. Leave empty for 'today'.
states	array	Filter by physical address state, 2-letter codes (e.g. TX, FL, CA). Leave empty for all states.
carrierOperation	string	Interstate carriers cross state lines (the classic freight market). Intrastate operate within one state only.
cargoTypes	array	Only carriers hauling at least one of the selected cargo types. Leave empty for all.
minPowerUnits	integer	Minimum number of power units (trucks/tractors). Leave empty for no minimum.
maxPowerUnits	integer	Maximum number of power units. Useful to target owner-operators (e.g. 1-5). Leave empty for no maximum.
requireEmail	boolean	Drop carriers without an email address. New carriers are ~100% covered; the older census is ~65%.
requirePhone	boolean	Drop carriers without a phone number (~97% have one).
maxResults	integer	Hard cap on dataset rows. Set to 0 for unlimited (full census pulls supported).
socrataAppToken	string	Optional free token from data.transportation.gov to lift anonymous rate throttling on very large pulls. Not needed for normal runs.

📤 Output

One row per carrier, saved to the dataset. Every row carries fetchedAt. The run's status message says how many leads were delivered and, when it stopped early or found nothing, why.

Field	Description
usdotNumber	Usdot Number
legalName	Legal Name
phone	Phone
cellPhone	Cell Phone
fax	Fax
email	Email
officer1	Officer1
officer2	Officer2
street	Street
city	City
state	State / province
zip	Zip
countyCode	County Code
country	Country
mailingStreet	Mailing Street
mailingCity	Mailing City
mailingState	Mailing State
mailingZip	Mailing Zip
powerUnits	Power Units
truckUnits	Truck Units
busUnits	Bus Units
totalDrivers	Total Drivers
cdlDrivers	Cdl Drivers
carrierOperation	Carrier Operation
hazmat	Hazmat
cargoTypes	Cargo Types
statusCode	Status Code
registrationDate	Registration Date
mcs150Date	Mcs150 Date
mcs150Mileage	Mcs150 Mileage
authorityType	Authority Type
authorityStatus	Authority Status
authorityReason	Authority Reason
authorityGrantedDate	Authority Granted Date
docketNumber	Docket Number
source	Source
fetchedAt	Fetched At

💼 Use cases

1. Insurance / factoring sales — target carriers by fleet size and status. Input: carrier names or numbers. Output: carriers + fleet + contact. Use: a lead list.

2. Logistics prospecting — find active carriers in a region. Input: carrier names. Output: carriers + operation. Use: a prospect list.

3. KYB / verification — verify a carrier by DOT/MC number. Input: the DOT/MC or name. Output: the canonical FMCSA record. Use: confirm authority.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/fmcsa-carrier-leads').call({"mode":"new_authorities","maxResults":1000});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/fmcsa-carrier-leads').call(run_input={"mode":"new_authorities","maxResults":1000})
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

Written for apify-client 3 for Python, where call() returns a run object; with version 1 or 2 it returns a dict — write run['defaultDatasetId'] there.

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your input → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: $0.004 per delivered carrier lead ($4 per 1,000). There is no start fee, so a run that delivers nothing costs nothing. If you set a maximum charge for a run (or run out of plan credit), the run stops at that amount and says so. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads the FMCSA motor-carrier registry (official open data).

What do I search by? By lead mode and filters: date range, state, cargo type, fleet size, operation, and whether a phone or email is on file. There is no lookup by carrier name or DOT number.

Why does search return only a few carriers? A date range in search keeps only carriers REGISTERED in that range. Leave the date range empty (all time) to search every active carrier.

How current is the data? Every run queries the source live, so results are as fresh as the registry.

What carrier data is included? DOT and MC numbers, fleet size, operation type, operating status, address and phone from the FMCSA.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

🐛 Troubleshooting

• Fewer rows than expected — read the status message: maxResults reached, the maximum charge reached, the timeout reached, or a date range that is too narrow.
• "No carriers matched" — the message lists the filters that were applied; widen the date range or drop one.
• "none of the states given is a US state" — use 2-letter codes (TX, FL, CA) or full names (Texas).
• Run FAILED with "FMCSA's open-data service did not answer" — the source was unavailable; leads already delivered stay in the dataset and are the only ones charged. Run again later.

⚖️ Is it legal to scrape this data?

This actor reads the public FMCSA motor-carrier registry. Results can still contain personal data (e.g. a person’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.1.15 — 2026-10-08 — README: the Python example works with the current Apify client

• The README's Python example read the results with run['defaultDatasetId']. With the current Apify client for Python (version 3) call() returns a run object, not a dict, and that line raised TypeError: 'Run' object is not subscriptable — after the run itself had finished. The example now reads run.default_dataset_id; with client version 1 or 2, keep run['defaultDatasetId']. Checked with apify-client 3.2.1, 2.5.1 and 1.12.2.
• No code, output field or pricing change.

0.1.14 — 2026-10-07 — a run that Apify starts again does not deliver a lead twice

• A run that the platform starts again no longer repeats what it has delivered. Apify can move a run to another server while it is going; the Actor then starts again from the top with the same dataset. Until now it delivered every lead again and counted from zero: in a test with maxResults 20000 that was started again after 6,500 rows, the dataset ended with 23,269 rows — about 9,500 leads written and charged twice. The Actor now first reads which leads its own dataset already holds; they count towards maxResults and are not written or charged again.
• No output field changed, no pricing change.

0.1.13 — 2026-10-06 — faster delivery, clean stops, clear messages

• Faster delivery. Rows are now delivered in batches together with their charge instead of one by one (two API calls per row). With the old way the 1,000-lead example took 87 s, and an unlimited pull reached only 4,969 rows before a 5-minute timeout.
• A run now stops cleanly when your maximum charge (or plan credit) is reached, with a status message that says so. Before, it kept going until the platform terminated the run.
• A run stops on its own shortly before the timeout and keeps what it delivered, instead of ending TIMED-OUT.
• Status message on every run: leads delivered, and why it stopped or found nothing ("No carriers matched (…)" lists the filters applied).
• States accept full names ("Texas" → TX). Before, a full name matched nothing and the run ended as an empty success with no explanation. Values that are neither a 2-letter code nor a US state name are ignored with a warning.
• Behaviour change — search now defaults to all time. The date range had a schema default of 7 days that also applied to search, so a search returned only carriers registered in the last week (240 for Texas on 2026-10-06) unless you changed it. The field has no default any more: empty means the last 7 days for the two "new" modes and all time for search. If you pass datePreset yourself nothing changes.
• A source failure ends FAILED with a plain message instead of a stack trace.
• README corrected: it described a lookup by carrier name or DOT number that this Actor never had, and listed "legal form" and "formation date" fields that do not exist. Pricing sentence now names the event and the price.
• No output field was renamed or removed. No pricing change.

0.1.12 — 2026-09-20 — README examples corrected against the real input schema

• The README's code examples did not match this Actor. They used queries and maxResultsPerQuery — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: {"mode":"new_authorities","maxResults":1000}
• The input table is regenerated from input_schema.json, so it lists the fields the Actor actually accepts.
• Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries query", and industry described as a NACE code.
• No code, output field or pricing change.

0.1 — 2026-09-07

• Dropped empty-promise columns. Removed dbaName, safetyRating, safetyRatingDate — FMCSA motor-carrier registry (official open data) does not carry them, so they were shipped as always-null columns. Only fields this source actually fills are now emitted.
• Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

0.0

• Initial release: data from the FMCSA motor-carrier registry (official open data) by name or registry ID.