# check_carrier_identity

> check_carrier_identity is a paid API for AI agents from fmcsa-mcp-843680657471.us-central1.run.app, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-14).

Investigates a USDOT number by surfacing all other USDOT numbers sharing contact identifiers with it and flagging any revocation or suspension history across those linked carriers.

## Facts

- Endpoint: POST https://fmcsa-mcp-843680657471.us-central1.run.app/x402/check_carrier_identity?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/check-carrier-identity-71376cd9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DczfS4T66Xe1yTF5T3JTZ

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 check-carrier-identity-71376cd9 -d '<json body>'
```

Example prompt: I think this carrier might have re-registered after a revocation — can you do a full identity check on USDOT number 3842917 and show me every other USDOT linked to the same contact info plus any revocation or suspension flags across those?

## When to prefer this

Use this endpoint when you need full forensic detail about a carrier's identity network — specifically the complete list of linked USDOT numbers and their revocation/suspension status. Prefer this over the free screen_carrier_identity endpoint when a suspicious signal has already been detected and you need evidence for a compliance decision, fraud investigation, or onboarding review. Not needed when you only want a quick flag and count — use screen_carrier_identity in that case to avoid the $0.05 charge.

## Known failure modes

- USDOT number does not exist or cannot be resolved — billed regardless of link count
- Invalid or non-integer USDOT number input returns a validation error
- Network timeout on the FMCSA data source causing incomplete results
- Carrier exists but has no resolvable contact identifiers — returns empty link set but still billed

## How this service works

Use this when a carrier looks suspicious — a name change, a new USDOT number tied to an old fleet, a business you suspect re-registered after a revocation — and you need the full evidence: every other USDOT number sharing a contact identifier with it, and whether any of them carries a revocation or suspension motive. Call the free screen_carrier_identity first if you only need the flag and a count. Billed whenever the USDOT number resolves, even with no links found.

## Output

Returns a list of all other USDOT numbers that share a contact identifier (such as phone, email, address, or EIN) with the queried carrier, along with an indicator of whether any linked carriers have a revocation or suspension record. Billed at $0.05 USDC per call whenever the USDOT number successfully resolves, even if no links are found.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "usdot_number": {
   "type": "integer",
   "description": "The carrier's USDOT number to check for shared identifiers with other carriers."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/check-carrier-identity-71376cd9/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)