LiveProductMarket: United States

id.Verify

Checks a carrier’s paperwork against the FMCSA federal record and shows where the two disagree — before the load moves.

id.Verify home screen: the headline “The carrier’s paperwork, checked against the federal record” and a sample report with a risk score of 44/100 and a Review verdict

The product home page

Problem

A broker receives a packet from the carrier: certificate of insurance, authority letter, rate confirmation, W-9, the driver’s CDL. Looking up the MC number proves the company exists — not that the paperwork is theirs, or that nobody edited it. That gap is where double brokering, lapsed authority and doctored certificates live.

Who it's for: US freight brokerages and their dispatchers.

What we built

  • Reads every page as an image, not as its text layer — so an amount typed over a certificate gets caught. Phone photos and scans welcome.
  • Identifies the carrier from the documents themselves, never from a number someone typed in.
  • Checks authority, insurance, safety rating and inspection history against FMCSA; the VIN against NHTSA; the legal name against the US Consolidated Screening List.
  • Returns a 0–100 score and a separate Pass / Review / Block verdict. Missing data is never penalised — the report says what is missing.
  • Issues a PDF report sealed on every page. Anyone holding a copy can upload it, no account needed, and see which fields differ from what was issued.
  • Team accounts and an API for the customer’s own systems.

Our role

The whole product: research, architecture, engineering, launch, billing and support.

Outcome

Live and publicly available, with subscriptions and a free trial. The interface is available in ten languages, including those spoken by drivers and dispatchers across the US market.

Stack

  • Next.js
  • Cloudflare Workers
  • Supabase
  • LLM OCR

Interfaces

An example check in the id.Verify dashboard on the invented carrier ACME TRUCKING LLC: high risk at 44/100, the check's stages from documents to sanctions lists, and findings with their points
A carrier check in the dashboard: stages, score and findings
The first page of an id.Verify PDF report on the invented carrier ACME TRUCKING LLC: a risk score of 44/100, a “Hold for manual review” verdict, and findings on sanctions screening, FMCSA and the driver’s CDL
The PDF report: score, verdict and sourced findings
The seal at the foot of an id.Verify report page: a QR code, the verification address verify.irsa.digital/v, the page number and a notice on how to check the report
A seal on every page, which is what a check reads
An id.Verify check of the sample report: “This is a sample report” — the square holds the words “test QR”, not a verification code, and the carrier is invented
Checking the sample report

Similar problem? Let's talk

Topic: id.Verify

For example, name@company.com or @username

Let’s talk

Leave a contact — we’ll reply with a next step.