The FMCSA QCMobile API is free, official, and genuinely useful for basic carrier lookups. But it has a 50-carrier query cap, no bulk access, no webhooks, no contact data, no tech stack, and no SLA. When you're building something real, you hit those walls fast.
AlphaLoops ingests the complete FMCSA census daily and layers proprietary intelligence on top — tech stack detection, verified contacts, fleet growth signals, risk monitoring, and webhooks. Sub-100ms response times across 2.4M+ carrier profiles.
200+ data fields per carrier. MCP server included. SDKs in Python and TypeScript.
Free REST API provided by FMCSA at mobile.fmcsa.dot.gov. Returns basic FMCSA census data — authority status, safety ratings, BASIC scores, and inspection summaries — in JSON format.
Free with a Login.gov webkey. Good for single-carrier lookups and compliance verification. Not designed for bulk processing or enriched carrier intelligence.
The FMCSA API covers what FMCSA collects. AlphaLoops starts there and adds the layer that production applications actually need.
| Capability | AlphaLoops | FMCSA QCMobile API |
|---|---|---|
| FMCSA data coverage | ||
| DOT number, MC number, legal name, DBA Core carrier identity fields
|
✓ Yes | ✓ Yes |
| Operating authority status Active, inactive, revoked, out-of-service
|
✓ Yes | ✓ Yes |
| Safety ratings and BASIC scores CSA BASIC percentiles, alert flags, deficiency indicators
|
✓ Yes | ✓ Yes — 5 BASICs reported |
| Inspection and out-of-service records Vehicle, driver, hazmat inspection counts and OOS rates
|
✓ Yes | ✓ Yes |
| Cargo carried and operation classification Cargo types, carrier operation type (for-hire, private, etc.)
|
✓ Yes | ✓ Yes |
| Production API capabilities | ||
| Bulk carrier access Query or download the full 2.4M+ carrier dataset
|
✓ Yes — nightly bulk exports | ✗ No — 50 carriers per query max |
| Webhooks and change monitoring Real-time alerts when authority, safety, or insurance changes
|
✓ Yes — event-driven webhooks | ✗ No — polling only |
| Uptime SLA and reliability Guaranteed availability for production applications
|
✓ Yes — commercial SLA | ✗ No — government infrastructure, no SLA |
| Published rate limits Documented request caps so you can plan your integration
|
✓ Yes — documented limits | ✗ No — undocumented throttling |
| Historical data access Authority history, insurance filing history, SMS trend data
|
✓ Yes | ✗ No — current state only |
| SDKs and MCP server Python, TypeScript, CLI, and MCP for AI agent workflows
|
✓ Yes — Python, TypeScript, CLI, MCP | ✗ No — raw HTTP only |
| Enriched carrier intelligence | ||
| Fleet size and power unit count Actual truck counts from FMCSA, continuously updated
|
✓ Yes | → Passenger vehicles only — no truck count field |
| Tech stack detection Samsara, Motive, McLeod, WEX, and 100+ freight-specific providers
|
✓ Yes | ✗ No — not in FMCSA data |
| Verified decision-maker contacts Names, emails, direct dials for carrier owners and fleet managers
|
✓ Yes | ✗ No — business phone only |
| Insurance filing details Coverage amounts, filing dates, insurer names, lapse history
|
✓ Yes | ✗ No — current status only |
| Fleet growth and contraction signals Track carriers adding trucks, hiring drivers, expanding authority
|
✓ Yes | ✗ No |
| AI-powered risk signals MC authority-for-sale, equipment liquidation, fraud indicators
|
✓ Yes | ✗ No |
| Carrier ICP scoring Score and rank carriers by fit for your specific product
|
✓ Yes | ✗ No |
| Cost | ||
| Pricing Annual contract
|
✓ Transparent — contact for pricing | ✓ Free |
The FMCSA QCMobile API returns what FMCSA collects: registration data, safety records, and authority status. FMCSA doesn't collect tech stacks, contact info, fleet growth trajectories, or insurance filing history. Those gaps aren't bugs — they're by design. For compliance verification, that's fine. For production carrier intelligence applications, it's the whole problem.
Name searches return a maximum of 50 carriers. There is no bulk endpoint and no way to download the full carrier dataset via the QCMobile API. Processing 2.4M carriers means 48,000+ serial requests with manual pagination using the start parameter — with no guaranteed throughput.
The QCMobile API runs on government infrastructure with no published SLA. FMCSA's own website has documented outages with notices stating "we have not established a time frame for restoring functionality." Third-party client libraries have a dedicated ErrSystemMaintenance error for this reason.
FMCSA does not publish rate limits. There is no documented requests-per-minute cap, no burst limit, and no headers indicating remaining quota. You can't plan your integration around limits that aren't documented — and undocumented throttling will silently fail your application.
FMCSA records a carrier's registered business phone. That's it. No decision-maker names, no direct emails, no mobile numbers. For any sales or outreach workflow, the FMCSA API gets you to the company door but not the right person inside it.
There is no way to subscribe to carrier changes. To monitor 10,000 carriers for authority revocations or safety rating changes, you must poll each one individually on a schedule — multiplying your request volume and your exposure to reliability issues.
The QCMobile API returns what carriers filed with FMCSA. Which telematics platform they run, what TMS they use, which fuel card they've adopted — none of that is in FMCSA data, so none of it is in the API. AlphaLoops tracks 100+ freight-specific technology providers across every carrier.
# To process 2.4M carriers via QCMobile name search: # 50 carriers per query → 48,000+ requests needed # No published rate limit → unknown throttling behavior # No bulk endpoint → sequential pagination only # No SLA → outages with no ETA for resolution # AlphaLoops alternative: # Nightly bulk exports → full 2.4M carrier dataset # Sub-100ms per-carrier API → 200+ fields per response # Webhooks → real-time change alerts, no polling # Commercial SLA → production-grade reliability
The FMCSA API is genuinely useful for specific use cases. Here's the honest breakdown.
The QCMobile API is free and sufficient for this. A single DOT number lookup returns authority status, OOS flags, and basic safety data in milliseconds. No need to pay for AlphaLoops if this is all you need.
QCMobile works for basic compliance lookups. If you need reliability guarantees, a commercial SLA, or enriched data alongside compliance status, AlphaLoops is the better infrastructure choice.
The QCMobile API is not designed for this. 50 carriers per query, no bulk endpoint, no documented rate limits. AlphaLoops provides nightly bulk exports and a production API built for this volume.
QCMobile has no webhooks. You'd be polling 10,000 endpoints on a schedule with no rate limit documentation. AlphaLoops provides event-driven webhooks for authority changes, safety rating updates, and out-of-service events.
None of that is in the FMCSA API — it only returns what FMCSA collects. AlphaLoops enriches every carrier with tech stack detection, verified contacts, fleet growth signals, and risk monitoring.
The QCMobile API is the right starting point. Free, official, and well-documented enough to get moving. When you hit its limits in production, AlphaLoops is ready.
200+ fields per carrier, bulk exports, webhooks, tech stack detection, verified contacts, and a commercial SLA.
Book a Demo