OrbTop

FMCSA L&I Broker Authority - MC Numbers, BOC-3, Insurance

LEAD GENERATIONBUSINESSOTHER
Try on Apify

FMCSA L&I Broker Authority - MC Numbers, BOC-3, Insurance

Scrape FMCSA Licensing & Insurance records: MC numbers, broker authority status, BOC-3 process agents, and insurance/bond summary. Look up by MC number, DOT number, or legal name. Joins to FMCSA SAFER via DOT number. Built for freight brokers, load boards, 3PLs, and carrier-vetting teams.

What it does

This actor queries the FMCSA Licensing & Insurance (L&I) portal (li-public.fmcsa.dot.gov) to extract carrier and broker authority records. For each lookup it retrieves:

  • MC/docket number and USDOT number
  • Legal name and DBA name
  • Business address, mailing address, and phone
  • Authority status (Common, Contract, Broker) — ACTIVE / INACTIVE / NONE
  • Carrier type flags (property, passenger, household goods, private, enterprise)
  • Insurance summary — BIPD (liability) required and on-file amounts
  • Cargo insurance and surety bond status
  • BOC-3 process agent status and blanket company name
  • Timestamp when the record was scraped

Use cases

  • Freight brokers & 3PLs — verify carrier authority and insurance before tendering loads
  • Load boards — enrich carrier profiles with authority and BOC-3 data
  • Factoring companies — confirm MC/DOT status before onboarding carriers
  • Compliance teams — bulk-check broker/carrier authority status for audit trails
  • FMCSA SAFER pairing — join to fmcsa-dot-crawler output via DOT number for complete safety + authority profiles

Lookup modes

Mode Input field Description
mc_number mcNumbers Look up by MC number (digits only, e.g. 3990)
dot_number dotNumbers Look up by USDOT number
legal_name legalName Substring search by legal name (min 3 characters)

Input

{
  "lookupMode": "mc_number",
  "mcNumbers": ["3990", "1304"],
  "maxItems": 10,
  "proxyConfiguration": { "useApifyProxy": true }
}

Important: Always leave proxyConfiguration set to Apify auto proxy. The FMCSA L&I portal blocks bare datacenter IPs and requires a residential or rotating proxy to reach.

Output

Each record is a flat JSON object:

{
  "mc_number": "MC00003990",
  "dot_number": "2959823",
  "legal_name": "BLUE NILE TRANSPORTS LLC",
  "dba_name": null,
  "city": "RESTON",
  "state": "VA",
  "business_address": "RESTON VA 20191",
  "business_phone": "703-555-1234",
  "mailing_address": null,
  "authority_status_common": "NONE",
  "authority_status_contract": "NONE",
  "authority_status_broker": "ACTIVE",
  "carrier_property": null,
  "carrier_passenger": null,
  "carrier_hhg": null,
  "carrier_private": null,
  "carrier_enterprise": null,
  "bipd_required": null,
  "bipd_on_file": null,
  "cargo_required": "N",
  "cargo_on_file": "N",
  "bond_required": "Y",
  "bond_on_file": "Y",
  "boc3_on_file": true,
  "blanket_company": "TRUCKERS NATIONWIDE INC",
  "scraped_at": "2026-05-09T04:30:28.000Z"
}

Technical notes

  • The FMCSA L&I portal uses server-rendered HTML (Oracle WebDB) with POST-based form submissions
  • Each lookup requires a reCAPTCHA v2 solve (handled automatically)
  • The portal is session-dependent: the detail page POST requires the same HTTP session as the preceding search POST
  • Proxy rotation is automatic on 403 responses (up to 3 retries per lookup)
  • Rate: approximately 25-40 seconds per record due to reCAPTCHA solve time

Pricing

  • $0.10 per run start
  • $0.002 per record scraped
Try on Apify