# FMCSA Carrier Safety Search - DOT KYB & Crash API (`pink_comic/fmcsa-carrier-safety-search`) Actor

Search official FMCSA carrier, inspection, violation, and crash records by company or USDOT for trucking KYB and insurance. Returns DOT/MC status, fleet, safety rating, OOS violations, and crashes. No key. Related: Business Entity Search, OSHA, OFAC.

- **URL**: https://apify.com/pink_comic/fmcsa-carrier-safety-search.md
- **Developed by:** [Ava Torres](https://apify.com/pink_comic) (community)
- **Categories:** Lead generation, Business, Agents
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## FMCSA Carrier Safety Scraper — DOT, Inspections & Crashes API

Search official **FMCSA carrier, inspection, violation, and crash records** by trucking-company name or exact USDOT number. The Actor uses public U.S. Department of Transportation datasets, requires no API key, and returns source-linked evidence for carrier onboarding, commercial-auto insurance, compliance review, and trucking lead workflows.

### What it returns

#### Carrier identity and operating evidence

- USDOT number, legal name, and DBA name
- Active, inactive, or pending registration status
- MC/MX/FF operating-authority docket numbers and status codes
- FMCSA safety rating and review dates when available
- Power units, trucks, buses, drivers, CDL drivers, mileage, and fleet size
- Phone, cell phone, fax, email, physical address, and mailing address when reported
- Hazardous-material indicator and reported cargo classifications

#### Latest inspection and violation evidence

- Inspection ID, report number/state, date/time, location, level, and facility code
- Total, driver, vehicle, and hazmat violation counts
- Driver, vehicle, hazmat, and total out-of-service counts
- Linked violation codes, descriptions, units, citation numbers, and out-of-service indicators
- Official record URLs for the inspection and source dataset

#### Latest crash-involvement evidence

- Crash report ID, number/state, date/time, location, city, and reporting agency
- Injury, fatality, tow-away, hazmat, and federal/state-recordable indicators
- Vehicle/configuration/road/weather/light source codes and reported event sequence
- Official crash-record URL

### Quick test

The strongest first-run workflow is an exact USDOT lookup:

```json
{
  "dotNumber": "54283",
  "fetchSafetyHistory": true,
  "maxInspections": 10,
  "maxCrashes": 10
}
```

Search by carrier name:

```json
{
  "carrierName": "Swift Transportation",
  "statusCode": "A",
  "fetchSafetyHistory": true,
  "maxResults": 10
}
```

Carrier-only lead search without secondary safety-history requests:

```json
{
  "carrierName": "Transport",
  "state": "TX",
  "statusCode": "A",
  "fetchSafetyHistory": false,
  "maxResults": 25
}
```

### Input

| Field | Required | Description |
| --- | --- | --- |
| `carrierName` | One of name/DOT | Searches legal and DBA names. |
| `dotNumber` | One of name/DOT | Exact USDOT lookup; takes precedence over name. |
| `state` | No | Two-letter physical-address state filter. |
| `statusCode` | No | `A` active, `I` inactive, or `P` pending for name searches. Exact USDOT lookups ignore this filter. |
| `fetchSafetyHistory` | No | Attach latest inspection, violation, and crash records. Defaults to `true`. |
| `maxInspections` | No | Latest inspections per carrier, 1–25. Defaults to 10. |
| `maxCrashes` | No | Latest crash reports per carrier, 1–25. Defaults to 10. |
| `maxResults` | No | Total carrier response cap, 1–100. |

If no carrier name or DOT number is supplied, the Actor uses deterministic Swift Transportation USDOT `54283`, so first runs and Store quality tests return current carrier and safety evidence quickly.

### Common workflows

- Carrier onboarding and USDOT/MC verification
- Commercial-auto insurance and transportation risk review
- Inspection and out-of-service violation research
- Reported crash-involvement screening
- Freight-broker and shipper carrier due diligence
- Trucking-company lead generation and fleet-size segmentation
- CRM/vendor-record enrichment and monitoring

### Evidence limits and responsible use

FMCSA records are screening evidence, not a complete or real-time safety determination.

- **Crash involvement does not establish fault or preventability.** A crash record shows reported involvement. It is not proof that the carrier or driver caused the crash.
- Inspection violations and citations can be corrected, challenged, settled, or adjudicated later.
- State and FMCSA reports can be delayed, duplicated, amended, or removed as corrections arrive.
- Driver data are excluded from the public inspection and crash files because of privacy restrictions.
- Safety ratings, operating authority, registration, inspections, violations, and crashes have different meanings and update schedules; do not collapse them into a single pass/fail conclusion.
- Output is bounded by `maxInspections` and `maxCrashes` and is not represented as complete history.

Review the linked official records and current FMCSA systems before making a safety, insurance, employment, or contracting decision.

### Official sources

- [FMCSA Company Census File](https://data.transportation.gov/Trucking-and-Motorcoaches/Company-Census-File/az4n-8mr2)
- [FMCSA Vehicle Inspection File](https://data.transportation.gov/Trucking-and-Motorcoaches/Vehicle-Inspection-File/fx4q-ay7w)
- [FMCSA Vehicle Inspections and Violations](https://data.transportation.gov/Trucking-and-Motorcoaches/Vehicle-Inspections-and-Violations/876r-jsdb)
- [FMCSA Crash File](https://data.transportation.gov/Trucking-and-Motorcoaches/Crash-File/aayw-vxb3)
- [FMCSA Data Dissemination Program](https://www.fmcsa.dot.gov/registration/fmcsa-data-dissemination-program)

# Actor input Schema

## `carrierName` (type: `string`):

Search legal and DBA names. Examples: Swift Transportation, J.B. Hunt, Werner Enterprises.

## `dotNumber` (type: `string`):

Exact USDOT number lookup. When provided, it takes precedence over Carrier Name.

## `state` (type: `string`):

Optional two-letter state filter, such as TX or CA.

## `statusCode` (type: `string`):

Optional FMCSA registration-status filter for carrier-name searches. Exact USDOT lookups return the carrier regardless of this UI default.

## `fetchSafetyHistory` (type: `boolean`):

Attach bounded latest public FMCSA MCMIS inspection, violation, and crash records to each carrier. Crash involvement does not establish fault.

## `maxInspections` (type: `integer`):

Maximum latest inspection records to attach to each carrier when safety history is enabled.

## `maxCrashes` (type: `integer`):

Maximum latest crash-involvement records to attach to each carrier when safety history is enabled.

## `maxResults` (type: `integer`):

Total response cap for carrier-name searches. Exact USDOT lookups return at most one result.

## Actor input object example

```json
{
  "statusCode": "A",
  "fetchSafetyHistory": true,
  "maxInspections": 10,
  "maxCrashes": 10,
  "maxResults": 25
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "fetchSafetyHistory": true,
    "maxInspections": 10,
    "maxCrashes": 10,
    "maxResults": 25
};

// Run the Actor and wait for it to finish
const run = await client.actor("pink_comic/fmcsa-carrier-safety-search").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "fetchSafetyHistory": True,
    "maxInspections": 10,
    "maxCrashes": 10,
    "maxResults": 25,
}

# Run the Actor and wait for it to finish
run = client.actor("pink_comic/fmcsa-carrier-safety-search").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "fetchSafetyHistory": true,
  "maxInspections": 10,
  "maxCrashes": 10,
  "maxResults": 25
}' |
apify call pink_comic/fmcsa-carrier-safety-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pink_comic/fmcsa-carrier-safety-search"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/uo09kuiiBk0DJQZhO/builds/wBHdXRXJZEaCAR5HL/openapi.json