New Trucking Carrier Leads — FMCSA New-Authority Feed

A brand-new motor carrier is the most sought-after cold-call in trucking — the day a carrier gets its USDOT authority, it's flooded by factoring, insurance, ELD, and fuel-card sales teams. This Actor gives you that list first: a daily feed of newly-registered US carriers — legal name, phone, address, fleet size — pulled from official FMCSA data. Only NEW carriers since your last run (not another bulk scraper), and no API keys required.

Built for freight-factoring & commercial-truck-insurance sales, ELD/dispatch and fuel-card vendors, and trucking-lead resellers who need fresh new-authority leads without a $129/month list subscription.

What you get

One carrier_lead row per newly-registered carrier:

{
  "type": "carrier_lead",
  "legal_name": "HODALE CARRIERS LLC",
  "dba_name": "",
  "phone": "5025551212",
  "cell_phone": "",
  "email": "ops@example.com",
  "address": "1 MAIN ST",
  "city": "LOUISVILLE",
  "state": "KY",
  "zip": "40202",
  "power_units": 2,
  "drivers": 3,
  "operation": "Authorized For Hire",
  "dot_number": "8574807",
  "docket": "MC1234567",
  "add_date": "2026-07-14",
  "first_seen": "2026-07-16"
}

Contact info ships in the source — the raw row is a callable lead, no enrichment step. Every run ends with a run_summary receipt (how many new, scope, whether the source was fully reachable), so "0 new today" is an explicit answer, never a blank table.

Why "new since last run" (not a bulk scraper)

This Actor remembers which carriers it has already delivered (in a private key-value store) and emits only carriers new since your previous run. Schedule it daily and you get a clean, deduplicated stream of fresh leads — the general FMCSA "download everything" scrapers make you diff it yourself.

Your first run — you choose

• Default (skipBacklog off): the first run returns every carrier in your lookback window — a one-time backlog batch (capped by Max leads), so you start with a list in hand. Subsequent runs deliver only the daily new arrivals.
• skipBacklog on: the first run silently records a baseline for free and delivers nothing; from then on you get only carriers registered after you started watching. Ideal if you want a pure going-forward feed and don't want to pay for (or wade through) the backlog.

How to use it

1. Pick your states (e.g. ["TX"]) or leave empty for all.
2. Choose operation type — Authorized For Hire are the prime insurance/factoring targets.
3. Optional: minimum fleet size, require a phone number, max leads (spend cap).
4. Run once for the recent window, or schedule it daily and pipe the dataset to your CRM, dialer, or a Google Sheet.

What this costs

Pay-per-result: a small actor-start fee + per new-carrier lead. Compare: TruckerDB sells new-DOT lists at $129/month; you pay only for the fresh rows in the states you want, on the schedule you want.

Data source & honest notes

• Source: FMCSA Company Census File on data.transportation.gov (dataset az4n-8mr2) — official US-government open data, refreshed daily, public. No scraping, no login, no CAPTCHA.
• "New" = new USDOT registration (add_date). A carrier registers for a USDOT number when it starts operating; that's the new-authority trigger this feed detects.
• ~2–3 day publish lag. FMCSA typically adds a new carrier to the public census 2–3 days after registration, so lookbackDays should stay ≥ 7 (the default). With the built-in diff, a wide window costs you nothing — each carrier is still emitted only once, the first run it appears; a too-narrow window (1–2 days) just misses carriers the census hasn't published yet.
• Contact fields come from the carrier's own FMCSA filing. Some rows lack a phone or email — use requirePhone to keep only directly-callable leads.
• Compliance is yours. These are business leads (carriers), addresses and public filing data only. Follow the rules that apply to you — TCPA/DNC for calls and texts, CAN-SPAM for email — and scrub against the DNC registry before dialing. New carriers are heavily solicited; call responsibly.
• Resilient by design: the FMCSA API is queried with retries and back-off; if it's briefly slow, the run returns a partial feed with a note and succeeds, rather than failing. Bad input returns a guiding receipt, not a crash. Every run's spend is capped by maxResults.

Roadmap

Authority status-change feed (out-of-service / revoked / reinstated) off the same source, insurance-lapse signals, and MC-authority-grant date (distinct from DOT registration) as a premium tier.