Put carrier-safety intelligence inside your software
VioCodes turns raw FMCSA records into a decision — a risk score, an approve/review/reject verdict, and the flags behind it. If you run a TMS, brokerage, or insurance platform, you can consume that same intelligence by API instead of sending people to look it up.
Where it fits
TMS & dispatch
Show a live safety verdict on every carrier your dispatchers touch — inside the software they already use.
Freight brokerages
Auto-screen carriers at load-assignment: approve, review, or reject against your own risk policy, no tab-switching.
Insurance & underwriting
Pull structured FMCSA safety intelligence — OOS rates, BASIC exposure, crash history — straight into your models.
Monitoring & alerts
Feed authority, insurance, and CSA changes into your own watch lists and notify your team when a carrier turns risky.
What you can consume
- Carrier search by name, USDOT, or MC/MX/FF — plus a full safety snapshot (authority, insurance, inspections, crashes, safety rating)
- A 0–100 risk score and approve / review / reject verdict with the exact flags behind it
- Bulk screening of many carriers at once against a configurable risk policy
- The complete carrier record: CSA breakdown, every inspection & violation with CSA points, and the connections graph (shared VINs, addresses, officers)
- Violation-code lookup + CSA point scoring (severity × time-weight) from SMS Appendix A
- Everything from free, current FMCSA public data — nothing resold
The public tools on this site — carrier lookup, bulk screening, the DataQs drafter — all run on the same intelligence. An API partnership just lets your product use it directly. Access is granted per-partner, so reach out and we’ll scope it together.
One call, a decision back
POST /screen
{ "usdots": ["1916638", "2407268"] }
→ 2407268 REJECT score 0
authority inactive · no BIPD
→ 1916638 REVIEW score 65
revocation pendingBring your own risk policy; get back a verdict, a score, and the reasons — not raw rows to re-interpret.
Full API reference — all endpoints →Let’s talk
I’m Yurii — a working trucking safety manager, and I build VioCodes myself. If you want to integrate this into your product, reach out directly and tell me what you’re building. I read and answer everything personally.
Prefer to browse first? See the current partner API reference or try bulk screening to feel the output shape.