Build Compliance
Into Anything.
One key connects your TMS, ELD, fleet platform, brokerage or insurance system to the decision engines behind every X3 Fleet Safety product. Raw data tells your software what happened. X3 tells it what that means and what to do next — grounded in verbatim 49 CFR, a 300,000+ record corpus and live USDOT data, with the citation attached.
Your Platform Has the Data. It Doesn’t Have the Judgment.
A TMS knows the load, the driver and the truck. An ELD knows the hours. A brokerage knows the DOT number. None of them know whether the carrier should be tendered, whether the log is a violation, whether the driver is qualified for this trip, or what 49 CFR actually says about it — and building a regulation team into a software product is a multi-year detour. So the platform shows the data and leaves the judgment to whoever is looking at the screen.
Every compliance product X3 ships runs on one engine. The API opens that engine to yours.
Send Data. Get a Decision.
Every X3 capability sits behind one key. Each engine returns a structured, cited decision your software can act on — not a page of search results, not an uncited paragraph.
The regulation, verbatim and cited. Query the exact controlling text of 49 CFR, refreshed as the eCFR changes — no hallucinated rules, no stale citations.
200+ compliance agents, the same specialists that power X3 HazMat, CSA, HOS, DataQ and Drug & Alcohol, each scoped to a real compliance job and grounded in the corpus.
A carrier’s authority, safety-rating factors and inspection signals by USDOT in one call — for TMS, insurers, brokers and factoring platforms.
Clear / Review / Hold, Preventable / Not preventable, cleared / not cleared — with the reasons, the rule and a confidence your product can render.
One key. Every X3 product.
One Call. A Cited Carrier Decision.
This is the live Carrier Intelligence engine — the same call behind X3 CarrierCheck. A sample response the way your software receives it, then the real endpoint you can hit right now.
vetting.authority_active: true·chameleon_links: []— authority confirmed, no fraud-network links foundbasics.unsafe_driving.percentile_pct: 86.5·alert: true— the BASIC that drives the risk scorequalification: "Review"— the verdict your product renders, with the reasons array attached- Every field grounded in FMCSA data and the X3 corpus, cited to the section it came from
Every X3 Product Runs on This Engine.
Now So Can Yours.
X3 CSA, DataQ, MVR, HOS, HazMat, CarrierCheck, Legal, Permits, Clean Truck and the rest of the twenty are not separate systems — they are twenty front doors on one engine. The API is that engine, opened to your software. Integrate once, and every answer a fleet can get on an X3 screen, your TMS, ELD, brokerage or insurance platform can get in a response, cited to the regulation. Carrier and Regulation Intelligence are live today; the rest switch on under the same key as each product is production-hardened.
Twenty products. One integration.
Can we tender to this carrier?
Behind it: X3 CarrierCheck, X3 CSA, X3 Insurability. Send a DOT#, get authority, the 7 BASICs, a risk score, fraud signals and a Clear / Review / Hold verdict.What does the regulation actually say?
Behind it: Ask X3 and the 300,000-record corpus. Ask a real DOT question, get the applicable sections, exceptions, risk flags and citations verified against the eCFR.Is this driver legal for this load?
Behind it: X3 Workforce, X3 MVR, X3 Drug & Alcohol, X3 Background. Send a driver profile, get a §391 eligibility call and the DQ-file gaps.Is this log a violation?
Behind it: X3 HOS. Send log data, get §395 violations, the 11/14/60-70 status and the corrective action.Can this truck take this route?
Behind it: X3 Permits, X3 HazMat, X3 Clean Truck. Send vehicle, route and cargo, get cleared / not cleared with the credentials and permits required.Was this crash preventable?
Behind it: X3 Preventability, X3 DataQ. Send the event, get Preventable / Not preventable under the ATA/NSC standard, the factors and the challenge packet.Does this document meet the CFR?
Behind it: X3 Verify, X3 SOP, X3 Legal. Upload a policy, SOP or driver file, get it classified, checked against the rule and marked up.Is this fleet audit-ready?
Behind it: X3 DOT Audit, X3 New Entrant. Send the fleet record, get readiness, the gaps ranked and the export an auditor accepts.Live in an Afternoon.
Simple REST and JSON. Search the CFR, ask an agent, pull a carrier by USDOT — and meter by call as you grow.
Get a key
Request a sandbox key and pick a plan later. Free dev tier to start, no card.
Call the endpoint
GET /api/carrier?dot=… for a carrier. GET /api/search?q=… for the rulebook. POST /api/specialist for an agent.
Read the decision
Structured JSON with the verdict, the reasons, the citation and a confidence — render it, gate on it, log it.
Ship it
Embed cited compliance intelligence in your product. Webhooks when something changes; a spend cap on every key.
Get a key. Call the endpoint. Ship it.
Watch. Don’t Poll.
The corpus refreshes as the eCFR changes and carrier data updates as FMCSA publishes. Subscribe to a carrier, driver or permit and X3 sends a webhook when something material changes — priced per monitored entity, so you never hammer the API to find out.
Verbatim 49 CFR refreshed as the eCFR changes; carrier data as FMCSA publishes.
A carrier, a driver, a permit — one entity, one line item.
A webhook with the change and the citation, not a diff you have to interpret.
A hard monthly spend cap on every key, with 50 / 75 / 90% alerts.
Your product shouldn’t find out about a revoked authority from the customer. The webhook tells it first.
Every X3 Compliance Domain. Behind One Key.
The 200+ grounded agents are organized into the same specialist crews that power each X3 Fleet Safety product. Call any of them by name over verbatim 49 CFR and live carrier data.
Not for fleets. For the software fleets use.
Not for Fleets. For the Software Fleets Use.
TMS and ELD platforms adding cited HOS and compliance answers inside dispatch. Insurers and MGAs pulling carrier safety factors by USDOT. Brokers and shippers vetting authority and catching fraud signals at onboarding. Factoring and fintech scoring carrier reliability inside credit flows. Consultants and internal teams grounding their own copilots in a source they can trust.
Your Product Ships With Compliance Judgment Built In.
The same engine behind every X3 Fleet Safety product, inside yours — cited answers your users can trust, decisions your workflows can gate on, and a bill that never surprises you.
One key reaches every engine; turn capabilities on as you grow.
Every answer tied to the section it came from.
A hard cap per key, alerts on the way up, no charge for failures.
Pay Only for What X3 Does.
A platform fee plus metered usage. Start free, build in the sandbox, go live when you’re ready — and every paid plan reaches the whole catalog.
- ✓All endpoints, sandbox data
- ✓Small live allowance
- ✓1 key
- ✓Every engine in the catalog
- ✓3 keys · webhooks
- ✓Standard rate limits
- ✓10 keys · batch · monitoring
- ✓Lower usage rates
- ✓Analytics · priority support
- ✓25 keys · bulk ops · SLA
- ✓Lowest usage rates
- ✓Priority processing
| Data lookup | $0.01 |
| Compliance decision | $0.10 |
| Deep AI / document analysis | by workload |
| Monitoring | per entity / mo |
| Third-party data (MVR, background, Clearinghouse) | at cost |
Decision support, not legal advice. X3 API returns cited, regulation-grounded information from published sources. It is not legal advice and is not affiliated with FMCSA or USDOT. Verify against the current controlling regulation.
Frequently Asked Questions.
What platform teams ask before they put X3 API behind their product.
Is this the same engine behind the X3 products?
How is it grounded?
What can I pull on a carrier?
Which engines are live today?
What are the rate limits and latency?
How does billing work?
How do you handle security and data?
How do I get started?
Build Compliance Into Anything.
Get a sandbox key, make the first call from the quickstart, and ship cited compliance intelligence inside your product this week.