FMCSA Carrier Verify avatar

FMCSA Carrier Verify

Pricing

from $8.00 / 1,000 carrier reports

Go to Apify Store
FMCSA Carrier Verify

FMCSA Carrier Verify

Verify US trucking carriers and freight brokers by USDOT or MC number: operating authority, insurance on file, out-of-service orders, safety rating, authority age, plus a PASS / REVIEW / FAIL verdict with reasons. Official FMCSA data, agent-ready JSON.

Pricing

from $8.00 / 1,000 carrier reports

Rating

0.0

(0)

Developer

Curtis Still

Curtis Still

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

20 days ago

Last modified

Features

Limited permissions

Share

FMCSA Carrier Verify — USDOT & MC carrier check API for brokers, shippers & AI agents

By SourceWire — clean, agent-ready data tools.

Verify any US motor carrier or freight broker in about a second. You get operating authority status, insurance on file vs. required, out-of-service orders, safety rating, authority age, revocations, and a PASS / REVIEW / FAIL / INCOMPLETE verdict with reason codes and findings that cite their FMCSA source and its timestamp.

Verdicts are based on six official FMCSA open datasets on data.transportation.gov (US federal public data, updated daily). Each carrier is also cross-checked against the public FMCSA SAFER Company Snapshot, with no login. If a required source fails, is empty or is out of date, the result is INCOMPLETE, never a PASS, and you are not charged.

Why use it

  • Fraud screening before you tender a load. Double brokering and identity theft usually show up as brand-new authority, a missing BIPD filing, a pending revocation, or an inactive USDOT number. Each of these becomes a flag.
  • Bulk carrier onboarding and monitoring. Run up to 10,000 USDOT or MC numbers on a schedule and alert on any carrier whose verdict changes.
  • Agent-ready output. One flat JSON object per carrier with a stable schema and a deterministic verdict, so an LLM agent can act on it without parsing HTML.

Use cases

  • Freight brokers & 3PLs: vet a carrier before tendering a load; catch double-brokering red flags (new authority, missing insurance, pending revocation).
  • Shippers & procurement: bulk-verify your carrier list and re-run on a schedule to catch changes.
  • Factoring, insurance & fintech: KYB-style checks on trucking companies at onboarding.
  • AI agents & MCP: give a ChatGPT/Claude/LangChain agent a reliable verify_carrier tool that returns a verdict instead of a web page.
  • Developers: drop-in carrier-check endpoint for TMS, load boards and Zapier/Make/n8n workflows.

Input

FieldTypeExampleNotes
dotNumbersstring[]["63585"]USDOT numbers
mcNumbersstring[]["MC311233"]MC/FF/MX dockets; bare digits mean MC
includeHistorybooltrueAdds the first-authority-granted date and revocation history
maxCarriersint500Cost safety cap
maxSourceAgeHoursint72If any FMCSA dataset used for a carrier was last updated longer ago than this, the result is INCOMPLETE (SOURCE_STALE). 1 to 720, default 72
{ "dotNumbers": ["63585", "4522887"], "mcNumbers": ["MC1820027"], "includeHistory": true, "maxSourceAgeHours": 72 }

Output (one dataset item per carrier)

Key fields: dotNumber, legalName, dbaName, usdotStatus, operation, entityType, location{city,state,zip}, powerUnits, drivers, hazmat, safetyRating, mcs150Date, dockets[], authority[]{docket, common, contract, broker, revocationPending, bipdRequiredUsd, bipdOnFileUsd, cargoOnFile, bondOnFile}, insuranceFilings[]{type, insurer, effectiveDate, policyNumber, form}, firstAuthorityGrantedDate, authorityAgeDays, revocations[], outOfServiceOrders[], verdict, legacyVerdict, partialVerdict, reasonCodes[], findings[]{code, severity, message, source, datasetId, url, sourceDataUpdatedAt, conflictingSources}, flags[], incompleteReasons[], explanation, billable, sources[]{dataset, url, ok, retrievedAt, sourceDataUpdatedAt, freshness, ageHours}, crossCheckSources[]{dataset, url, retrievedAt, informationAsOf, crossCheckResult}, sourceUrls[], checkedAt, schemaVersion.

Shortened examples from a real run on October 28, 2026 (version 1.2.3):

{"dotNumber":"3111464","legalName":"DAY & NIGHT TRUCKING INC","usdotStatus":"ACTIVE","verdict":"FAIL",
"reasonCodes":["NO_ACTIVE_AUTHORITY"],
"flags":["Safety rating CONDITIONAL",
"For-hire interstate carrier with no ACTIVE operating authority",
"MCS-150 not updated in 2 years (biennial update required)"],
"billable":true}
{"dotNumber":"999999999","found":false,"verdict":"FAIL","reasonCodes":["CARRIER_NOT_FOUND"],"billable":false}

Verdict rules

A FAIL, REVIEW or PASS is only given when the data it depends on was retrieved successfully and is current. Otherwise the result is INCOMPLETE.

  • FAIL: verified from current data: USDOT inactive; active out-of-service order; UNSATISFACTORY rating; authority revocation pending; BIPD on file below the required minimum; broker bond missing; a for-hire interstate carrier with no active authority. Also FAIL with reason CARRIER_NOT_FOUND when both the Census and L&I lookups succeeded and neither has the number. Treat it as high risk, not as an error. Not charged.
  • REVIEW: CONDITIONAL rating; authority under 180 days old; application pending; cargo insurance required but missing; MCS-150 not updated in over 2 years; authority history not checked (includeHistory=false); or SOURCE_CONFLICT, meaning the sources disagree. That covers L&I authority against the authority history, and the SAFER Company Snapshot against L&I, Census or the out-of-service orders. A conflict finding lists both sources, the value each one shows and their timestamps.
  • PASS: all six required datasets were retrieved live and are newer than maxSourceAgeHours, required fields are present, and none of the above applies. This is not an endorsement. Always confirm on SAFER before tendering.
  • INCOMPLETE: required data was missing, empty, out of date (older than maxSourceAgeHours) or unavailable, for example a timeout, rate limit or server error from a source, or no record for a carrier that needs one. Reasons are in incompleteReasons (for example SOURCE_UNAVAILABLE, SOURCE_STALE, REQUIRED_RECORD_MISSING). partialVerdict shows what the available data pointed to, but it is not a verdict. Never charged. A failure verified from current data is still returned as FAIL.

The SAFER cross-check can only move a result toward REVIEW. It never creates a PASS, and it never downgrades a verified inactive-USDOT or out-of-service FAIL. If SAFER is down or its page can't be read, the verdict is based on the six datasets alone and crossCheckSources says so.

Backward compatibility: legacyVerdict keeps the pre-1.2 names (PASS_BASIC_CHECKS for PASS, NOT_FOUND for a not-found FAIL; other verdicts unchanged) for older integrations. New integrations should read verdict.

Pricing

Charged per carrier that gets a PASS, REVIEW or FAIL result. Not charged: numbers FMCSA has no record of (CARRIER_NOT_FOUND), MC dockets that can't be matched to a carrier, and INCOMPLETE results. Each item's billable field shows whether it was charged. See the Pricing tab for the current price.

For AI agents (LLM usage notes)

  • MCP: add https://mcp.apify.com/?tools=sourcewire/fmcsa-carrier-verify to your MCP client (Claude Desktop, Cursor, etc.) and the agent gets a carrier-verification tool.
  • Call this actor via the Apify MCP server (mcp.apify.com) or the Apify API with {"dotNumbers": [...]}. Read verdict first, then reasonCodes and findings.
  • FAIL with CARRIER_NOT_FOUND means FMCSA has no record. Treat it as high risk, not as an error.
  • INCOMPLETE means the carrier was not verified. Never present it as a pass; retry later.
  • SOURCE_CONFLICT means FMCSA sources disagree. Say which ones (see findings[].conflictingSources).
  • Insurance amounts are in USD. coverageUsd is often null, because FMCSA publishes many filings, such as surety bonds, with a 0 amount.
  • A cargo filing can be on file when not required. That is fine.

Privacy

By design, this actor does not return phone numbers, fax, email addresses, company officer names, or street addresses, even though some of them appear in the source data. It returns business-level compliance data only.

Limitations

  • Source datasets refresh daily, so changes made on SAFER today may appear tomorrow.
  • The SAFER cross-check reads a public HTML page. If SAFER changes its layout or is down, the cross-check reports UNAVAILABLE and the verdict is based on the FMCSA datasets alone. The SAFER snapshot date can lag the datasets by a day or two.
  • These are basic compliance checks, not a full identity or fraud investigation (no VIN, ELD, or contact verification).
  • Not legal advice.

Data sources

FMCSA Company Census (az4n-8mr2), L&I Carrier (6eyk-hxee), Active Insurance (ypjt-5ydn), Authority History (9mw4-x3tu), Revocations (sa6p-acbp), and Out-of-Service Orders (p2mt-9ige), all on https://data.transportation.gov. Cross-check: FMCSA SAFER Company Snapshot (https://safer.fmcsa.dot.gov). Set the optional env var SOCRATA_APP_TOKEN for higher rate limits.

How to call it via API

curl -X POST "https://api.apify.com/v2/acts/SourceWire~fmcsa-carrier-verify/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
-H "Content-Type: application/json" -d '{"dotNumbers":["63585"]}'

About SourceWire

SourceWire builds small, reliable data tools for AI agents and automation — official public data, stable JSON schemas, no fluff. Questions or feature requests? Open an issue on this Actor's Issues tab.