DOT# · commercial-vehicle identification

Carrier identity when plates and transponders fail.

Tollscopic DOT# reads USDOT and carrier markings from side-fire video, resolves the carrier against FMCSA records, and emits structured identity events with evidence, confidence, and explicit refusal classes.

Side-fire video FMCSA catalog Multi-field evidence Explicit abstention
01 · The leak

Commercial vehicles can use the road and still leave no invoiceable identity.

A toll system can know that a commercial vehicle crossed the toll point and still fail to produce an invoiceable identity. The plate path can fail. The transponder path can fail. The back office is left with a violation record and no party to invoice.

The vehicle was here. The system captured the pass. But the plate read was damaged, the transponder was missing, the DMV path was unresolvable, or the back office had no usable account.

Across commercial traffic, those unresolved records matter more than passenger misses. Each case has higher revenue impact, and each one walks away unless a second identity path exists.

The residue
A passage is captured. An identity is not.
This residue — commercial-vehicle passes that the primary path cannot close — is what Tollscopic DOT# is built to address. Higher revenue impact per case, and harder to invoice without a second signal.
How a commercial pass leaks
Plate read
damaged · obscured · misread
no usable plate string
Transponder
missing · expired · unread
no transaction
DMV / account lookup
plate not resolvable
no responsible party
Commercial-vehicle pass. No invoiceable identity. Revenue leak.
02 · The alternate signal

The vehicle already carries another identifier.

The commercial vehicles Tollscopic DOT# targets are regulated carrier vehicles expected to display carrier identity markings, including a USDOT number. Those markings connect to FMCSA carrier records — a second identity signal when plate and transponder paths fail.

fifth-wheel TRACTOR DOOR NORTHRIDGE FREIGHT CO USDOT 3847129 MC-71458 · TOLEDO OH USDOT NUMBER CARRIER NAME AUTHORITY · MC DOMICILE · CITY/STATE
synthetic carrier
Fields on the panel
USDOT number
primary federal carrier identifier
Carrier name
legal or trade name · often the cleanest field
Authority number
MC / MX / FF where present · not guaranteed
Domicile
city · state · supporting evidence and tie-breaker
Anchor: 49 CFR 390.21 · FMCSA Company Census File
03 · The technical insight

Identification is not OCR-then-lookup.

Catalog-constrained decoding of noisy multi-field evidence. That sentence is the product.

01
OCR makes structured errors

One wrong digit can name a completely different carrier. Side-fire angle, glare, and motion blur produce predictable confusions.

02
One frame is the wrong unit

A truck is visible for many frames. Picking one and dropping the rest throws away independent evidence about the same physical vehicle.

03
USDOT is one field among many

The same panel carries authority number, legal name, domicile, and supporting markings — each with different error modes.

04
FMCSA makes the problem finite

The carrier is a candidate in a public catalog plus an explicit "not in catalog" outcome. That constraint changes the math.

04 · System flow

From side-fire video to carrier event.

Six stages. Each subpage opens up one of them. Deeper detail lives behind the deep-dive cards below.

01 Side-fire camera

Captures the door panel as the vehicle passes.

02 Edge track package

Tracks the vehicle, gates commercial candidates, selects evidence frames.

03 Cloud extraction

Per-frame and cross-frame field observations with uncertainty preserved.

04 FMCSA shortlist

Retrieves plausible carrier candidates plus an explicit out-of-catalog option.

05 Joint scorer

Scores evidence against candidates. Multi-field agreement, runner-up gap, refusal.

06 DOT identity event

Structured event with confidence class, evidence, provenance, and usage policy.

05 · What the event gives you

A carrier identity event you can audit.

The output is not just a string. It is a structured record with evidence, provenance, and a usage contract that downstream systems can rely on.

identity_event · VERIFIED schematic
RESOLVED CARRIER
Northridge Freight Co
USDOT 3847129 · MC-71458 · Toledo, OH
site_id plaza_42 · lane_3
confidence 0.94 · gap 0.31 over runner-up
fields_observed usdot · name · authority · domicile
evidence_frames 6 selected from track of 24
catalog_snapshot fmcsa-cf-2026-05-19
model_ver dotnum-2026.05-a
identity_usage_policy
✓ correlation ✓ review · alert · billing
What it carries
Everything a reviewer needs to defend or replay the decision.
Site · lane · timestamp
where the pass happened, when
Carrier candidate or refusal
one outcome from the confidence family
Evidence frames
selected from the vehicle track
Fields observed
USDOT · authority · name · domicile, with per-field confidence
Catalog snapshot
the FMCSA version used at decision time
Model · scorer · config
versions that produced the result
Usage policy
what downstream systems are allowed to do

Bring us the violation queue. We will show what Tollscopic DOT# would find.

Audit-only deployment is a real entry point. We run on your traffic, measure carrier resolution on your unresolved commercial-vehicle records, and turn the activation conversation into data.