# FMCSA Carrier Selection Record

> FMCSA Carrier Selection Record is a paid API for AI agents from fmcsa-mcp-843680657471.us-central1.run.app, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-15).

Creates a dated, hashed, tamper-verifiable snapshot of FMCSA public data for a carrier (authority, insurance, safety rating, inspections, crashes, recent changes) to document a carrier-selection decision.

## Facts

- Endpoint: POST https://fmcsa-mcp-843680657471.us-central1.run.app/x402/get_carrier_selection_record?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fmcsa-carrier-selection-record-6eb747bc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap__r4pGjNkdi7ZKaFLGBSok

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability fmcsa-carrier-selection-record-6eb747bc -d '<json body>'
```

Example prompt: Pull a dated, hashed FMCSA carrier selection record for USDOT number 3481920 — I need a verifiable compliance snapshot I can file to document my carrier vetting decision.

## When to prefer this

Choose this endpoint when you need a compliance-grade, dated, hashed document that can serve as auditable evidence of a carrier-selection decision — not just a live lookup. It is the right choice over lookup_carrier or get_inspection_crash_summary when you need the record to be tamper-verifiable (with a verify link), when you need a single consolidated snapshot across authority, insurance, safety rating, inspections, crashes, and identity screens, and when the output may need to be filed, stored, or produced in an audit. Prefer lookup_carrier for a quick live profile check, and this endpoint when you need a defensible compliance artifact.

## Known failure modes

- USDOT number does not resolve in FMCSA data — no charge is incurred and no record is returned
- Invalid or non-integer USDOT number provided — request rejected before billing
- Carrier exists but has incomplete FMCSA data — partial record returned with missing fields flagged
- FMCSA data source temporarily unavailable — service returns an error without billing

## How this service works

Use this to document a carrier-selection decision: one dated, hashed record of what public FMCSA data shows about a carrier (authority, insurance flags, FMCSA safety rating and its date, inspections and out-of-service rates, crashes, the last year's changes, identity-linkage screen), with a free verify link that confirms the record is unaltered. A record, not a score or a recommendation. Billed only when the USDOT number resolves.

## Output

A dated, cryptographically hashed record containing the carrier's FMCSA authority status, insurance flags, safety rating and its effective date, roadside inspection counts, driver and vehicle out-of-service rates, crash counts, the past year's notable changes, and an identity-linkage screen. Also includes a free verification link that lets anyone confirm the record content is unaltered. Billed only when the USDOT number successfully resolves.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "usdot_number": {
   "type": "integer",
   "description": "The carrier's USDOT number."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fmcsa-carrier-selection-record-6eb747bc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from fmcsa-mcp-843680657471.us-central1.run.app](https://www.zero.xyz/host/fmcsa-mcp-843680657471.us-central1.run.app/llms.txt)