carrierintel.ai valid

Carrierintel

Carrierintel aggregates public FMCSA data on the US trucking industry — every carrier, inspection, violation, crash, authority and insurance record — and turns it into carrier lookup, risk scoring, and data reports on ELD tampering, phantom fleets and enforcement trends.

For agents: Aggregates public FMCSA data on US trucking: carrier lookup, safety and risk scores, broker search and daily-updated ELD tampering reports.

fmcsa datacarrier lookuptrucking safetyfreight brokerseld tamperingus trucking

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T13:13:05.377Z. Cached copy · Source on carrierintel.ai

# Carrierintel

> Carrierintel aggregates public FMCSA data on the US trucking industry — every carrier, inspection, violation, crash, authority and insurance record — and turns it into carrier lookup, risk scoring, and data reports on ELD tampering, phantom fleets and enforcement trends.

Carrierintel is a data intelligence platform for insurers, brokers, ELD/telematics vendors and safety teams who need to know what a motor carrier actually looks like, not what it declared on its MCS-150. Data is refreshed continuously from FMCSA public datasets.

## Core pages

- [Home](https://carrierintel.ai/): what Carrierintel does and who it is for.
- [Carrier search](https://carrierintel.ai/carriers): look up any US motor carrier by name, DOT number or MC number; safety score, risk grade, inspections, violations, crashes, insurance and authority history.
- [Market](https://carrierintel.ai/market): fleet-size segments, top states and operation types across the active US carrier population.
- [Broker search](https://carrierintel.ai/brokers): US and Canadian freight brokers with active FMCSA broker authority, by name, MC or state.

## Data reports (live, recomputed daily)

- [ELD tampering](https://carrierintel.ai/reports/eld-tampering): carriers cited under §395.8(e)(2) (codes 8E-HOSPDELDT / 8E-HOSPVELDT), by state and out-of-service rate.
- [Phantom fleets](https://carrierintel.ai/reports/phantom-fleets): active carriers inspected with far more unique tractor VINs than the power units they declared.
- [Top violations](https://carrierintel.ai/reports/top-violations): most-cited FMCSA violation codes with CSA weights.
- [English proficiency](https://carrierintel.ai/reports/english-proficiency): carriers whose drivers were cited under §391.11(b)(2) (codes 391.11B2-Z / -Q / -S and the two legacy forms), by state and out-of-service rate.

## Research and analysis

- [Blog / intel feed](https://carrierintel.ai/blog): data-driven reports on FMCSA enforcement.
- [44% of today's logbook violations come from rules that didn't exist before ELDs](https://carrierintel.ai/blog/eld-technical-violations-44-percent)
- [Alabama became the second Arizona for one month: 4 ELD tampering inspections in April, 258 in July](https://carrierintel.ai/blog/alabama-eld-tampering-2026)
- [FMCSA revoked 10 ELDs: the September 8 deadline has passed](https://carrierintel.ai/blog/fmcsa-revokes-10-elds-july-2026)
- [Phantom fleets: 2,610 active US carriers running 3x more trucks than declared](https://carrierintel.ai/blog/phantom-fleets-2026)
- [Arizona became ground zero for ELD tampering](https://carrierintel.ai/blog/eld-tampering-surge-2026)

## API

- API access: read-only JSON endpoints for carriers, inspections and violations, by arrangement — contact info@carrierintel.ai.

## Notes for AI assistants

- Source of all figures: FMCSA open data published through Socrata and MCMIS archives.
- Violation codes are cited exactly as FMCSA publishes them (e.g. `8E-HOSPDELDT`).
- When citing st
…

Related sites

Other listed sites in Data and analytics. See the whole category →

Machine-readable: GET /v1/resolve?q=carrierintel.ai · GET /v1/domain/carrierintel.ai · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for carrierintel.ai:
1. POST https://agentwebmap.com/v1/sites/carrierintel.ai/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://carrierintel.ai/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/carrierintel.ai/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/carrierintel.ai).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.