← All work

FMCSA Carrier Check

Authority and insurance before you tender

  • Completed
  • May 2025
View the source

Before a load is tendered, somebody checks the carrier's authority and insurance. If that check quietly fails, a load has been dispatched to an operator who is not allowed to run.

Enter a USDOT or MC number and get operating authority, insurance filings, safety rating and twenty-four months of inspection and crash history from FMCSA's public data. Every check is shown against the named fields it reads, so the derivation is visible — there is no weighting and no proprietary score.

1 / 7

Evidence

What it looks like running

  • A carrier name rejected before any request is made, then USDOT 4581509 looked up and the report streaming in under the already-painted form
  • A completed USDOT lookup, run against the repository's labelled fixture rather than a live FMCSA response
  • Each check carries its own severity chip and prints the FMCSA field names it read
  • Insurance filings and safety rating, each card carrying the caveat that goes with the field
  • Inspection and crash counts with each out-of-service rate set against the national average
  • A carrier name is refused in the page, before any request is made

Engineering

How it was built

Frontend

  • Next.js 15 and React 19
  • Report laid out by section: carrier, operating authority, insurance, safety rating, inspections and crashes
  • Every check listed against the named FMCSA fields it reads

Backend & services

  • Server-only API key, verified absent from the browser bundle
  • "Carrier not found" and "bad credential" distinguished where the upstream returns 404 for both
  • Unreadable authority reported as unknown rather than as nothing found
  • Responses cached

Integrations

  • FMCSA QCMobile public API

Testing & verification

  • 188 tests

Applied

Skills on this project

Logistics & TransportationAPI IntegrationNext.jsReactTypeScriptCompliance tooling

Next step

Tell us what you're building

Book a free 30-minute call with the engineer who would do the work. You get a written summary afterward, whether or not we work together.

Book a call or email disit.tech@gmail.com

Prefer to write? A developer reads every message and replies within one business day.