# FMCSA Carrier Profile Lookup by USDOT Number

> FMCSA Carrier Profile Lookup by USDOT Number is a paid API for AI agents from fmcsa-mcp-843680657471.us-central1.run.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-14).

Retrieves a trucking carrier's current FMCSA profile—safety rating, operating authority status, insurance flags, and fleet size—given its USDOT number.

## Facts

- Endpoint: POST https://fmcsa-mcp-843680657471.us-central1.run.app/x402/lookup_carrier?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/fmcsa-carrier-profile-lookup-by-usdot-number-12c60ece
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_M5fEfic9xWeMDmxfR6NRu

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-profile-lookup-by-usdot-number-12c60ece -d '<json body>'
```

Example prompt: Can you pull up the FMCSA profile for the carrier with USDOT number 3421567? I want to check their safety rating, authority status, and insurance flags before we assign them a load.

## When to prefer this

Use this endpoint when you already have a carrier's USDOT number and need their current regulatory profile. Prefer it over search_carriers when you have a specific USDOT to resolve, and over check_carrier_identity when you need the full profile rather than a targeted identity-verification check. Ideal for pre-load vetting, onboarding due diligence, and periodic compliance monitoring of known carriers.

## Known failure modes

- Unknown USDOT number returns no carrier record (no charge applies)
- Network or service timeout if FMCSA upstream is slow
- Stale data if FMCSA records have not been recently refreshed
- Payment failure if USDC balance is insufficient for the $0.01 charge
- Invalid input type if usdot_number is not provided as an integer

## How this service works

Use this when you already have a carrier's USDOT number and need its current profile: safety rating, authority status, insurance flags, fleet size. Returns Active, Inactive, and Pending carriers alike. Billed only when the number resolves to a real carrier; an unknown number is free.

## Output

Returns the carrier's current FMCSA profile including operating status (Active, Inactive, or Pending), safety rating tier, operating authority status, insurance flags, fleet size, and registered legal name and DBA name. If the USDOT number does not resolve to any known carrier, the call is free and an error or empty result is returned.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "claimed_zip": {
   "type": "string",
   "description": "Optional, part of an address claim."
  },
  "claimed_city": {
   "type": "string",
   "description": "Optional, part of an address claim."
  },
  "claimed_name": {
   "type": "string",
   "description": "Optional. A name to confirm against the carrier's own records (legal_name or dba_name) without ever receiving the value on file — e.g. to catch a carrier-identity-theft attempt."
  },
  "usdot_number": {
   "type": "integer",
   "description": "The carrier's USDOT number (its FMCSA registration number)."
  },
  "claimed_state": {
   "type": "string",
   "description": "Optional, part of an address claim."
  },
  "claimed_street": {
   "type": "string",
   "description": "Optional, part of an address claim."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/fmcsa-carrier-profile-lookup-by-usdot-number-12c60ece/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)