# FMCSA Carrier Search: US DOT Trucking Company Leads (`actor-forge/fmcsa-carrier-search`) Actor

Search the FMCSA Company Census (4.5M US DOT registrations) by state, city, fleet size, drivers, cargo, hazmat, operation and new-registration date: DOT and MC numbers, legal and DBA name, address, fleet and driver counts, safety rating, dates, company phone and e-mail. $1 per 1,000 carriers.

- **URL**: https://apify.com/actor-forge/fmcsa-carrier-search.md
- **Developed by:** [ActorForge](https://apify.com/actor-forge) (community)
- **Categories:** Lead generation, Business
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 carrier 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 Search: US DOT Trucking Company Leads

Search the FMCSA Company Census (4.5M US DOT registrations) by state, city, fleet size, drivers, cargo, hazmat, operation and new-registration date: DOT and MC numbers, legal and DBA name, address, fleet and driver counts, safety rating, dates, company phone and e-mail. $1 per 1,000 carriers.

**An FMCSA carrier search for US trucking leads, straight from the official Company Census.** The FMCSA Company Census File lists every **USDOT registration**, about 4.5 million carriers, brokers, shippers and freight forwarders, and is published as open data on data.transportation.gov. Filter by **state and city**, **fleet size (power units)**, **driver count**, **cargo carried** (general freight, refrigerated food, livestock, hazmat…), **interstate or intrastate**, for-hire only, entity type, name, and **new registrations in the last N days**, and get one clean row per registration: **USDOT and MC numbers**, **legal and DBA name**, status, entity types, operation and classifications, **physical city, state and ZIP** (street for companies), mailing city, **power units, trucks, buses, drivers and CDL drivers**, mileage, hazmat flag, cargo list, **safety rating**, registration and last MCS-150 dates, the SAFER snapshot link, and for companies the **business phone and e-mail**. Sort by newest or by largest fleet. Use it for **freight broker and carrier sales prospecting**, new-authority lead lists for insurance, fuel cards, factoring, ELD and dispatch services, carrier vetting, and transportation market research. **$1 per 1,000 carriers**, with no compute bill on top; problems return a free status row instead of failing.

### What data does it return?

Every run outputs clean, schema-validated rows like these:

| dotNumber | legalName | city | state | powerUnits | addedAt |
| --- | --- | --- | --- | --- | --- |
| 6393084 | ALLIANCE LIFTING AND TRANSPORT, LLC | El Paso | TX | 34 | 2026-10-20 |
| 6990988 | TITAN TRANSIT GROUP INC. | Fulshear | TX | 22 | 2026-10-17 |
| 6463740 | KW LOGISTICS LLC | Bertram | TX | 10 | 2026-10-16 |

### How much does it cost?

Transparent pay-per-event pricing — you only pay for what you get, and the
actor **always respects your run budget**: set a maximum total charge and it
stops cleanly at the cap instead of overrunning.

| Event | Price | Charged | Worked example |
| --- | --- | --- | --- |
| `carrier-result` | $0.001 | per carrier row | 1,000 carriers = $1.00 |
| `apify-actor-start` | $0.00005 | per run per GB of memory (platform start fee) | One run at 256 MB = $0.00005 |

### Input options

| Field | Type | Required | Default | Description |
| --- | --- | --- | --- | --- |
| `states` | array | no | — | 2-letter state codes of the physical address, e.g. TX, CA, FL. |
| `cities` | array | no | `[]` | Optional city names, e.g. Dallas, Houston (combine with states). |
| `dotNumbers` | array | no | `[]` | Look up specific registrations by USDOT number (digits only). |
| `nameContains` | string | no | `""` | Only registrations whose legal or DBA name contains this text, e.g. LOGISTICS, EXPRESS. |
| `status` | string | no | `"active"` | USDOT status. |
| `operation` | string | no | `"any"` | Carrier operation. |
| `entityTypes` | array | no | `[]` | Only registrations of any of these types. Empty = all. |
| `authorizedForHireOnly` | boolean | no | `false` | Only for-hire carriers (they haul for others), not private fleets. |
| `minPowerUnits` | integer | no | `0` | Fleet size floor. 0 = no minimum. |
| `maxPowerUnits` | integer | no | `0` | Fleet size ceiling. 0 = no maximum. |
| `minDrivers` | integer | no | `0` | Driver-count floor. 0 = no minimum. |
| `addedWithinDays` | integer | no | `0` | Only USDOT numbers added in the last N days (new carriers and new authorities). 0 = any date. |
| `hazmatOnly` | boolean | no | `false` | Only registrations flagged as carrying hazardous materials. |
| `cargo` | array | no | `[]` | Only carriers hauling any of these cargo types. Empty = all. |
| `companiesOnly` | boolean | no | `false` | Leave out individuals (owner-operators registered under their own name). |
| `includeContacts` | boolean | no | `true` | Add the phone and e-mail from the census for companies (corporations, partnerships, LLC/INC names). Never output for individuals. |
| `sortBy` | string | no | `"newest"` | Order of the results. |
| `maxItems` | integer | no | `200` | Stop after this many registrations. Each one is one charged row. |

### Limits & honest notes

- **Responsible use:** you are responsible for using the data in line with US law, including the TCPA and CAN-SPAM for calls and e-mails, and any state privacy laws. This actor is not affiliated with, endorsed by or sponsored by the FMCSA or the US Department of Transportation.
- It queries the public Socrata API of data.transportation.gov (dataset az4n-8mr2, keyless), which robots.txt allows, at about one request per second (the site's Crawl-delay), 1,000 rows per request. No login, no cookies, no proxies; it sends an honest user agent (ActorForge-FMCSA).
- Privacy by design: company officer names, cell phones and fax numbers are never requested. Many registrations are owner-operators under their own name: for those (and any registration without a company legal form) the street, phone and e-mail are left out. Turn on Companies only to skip individuals entirely.
- The census is refreshed by the FMCSA regularly but is not live: for real-time operating authority or insurance status, check the SAFER link on each row. A broad search (for example all of Texas) has tens of thousands of rows: set Max carriers to what you need.
- If the site answers with a block, the run stops at once, keeps the rows already delivered and adds a free status row. Respects your run budget: set a maximum total charge and the run stops cleanly at the cap. A run with no results returns one free status row.

### Related ActorForge actors

- [UK Companies House Search](https://apify.com/actor-forge/uk-companies-house-search) — the same kind of new-company lead lists for the UK
- [Domain Enrichment for Clay](https://apify.com/actor-forge/domain-enrichment) — tech stack and socials for carrier websites

### Changelog

- **2026-10-23** — Initial release: SoQL filters (states, cities, DOT numbers, name, status, operation, entity type, for-hire, fleet, drivers, new registrations, hazmat, cargo), newest/largest sort, DOT/MC, fleet, safety rating, dates, company-only contacts; free status rows.

***

*Built and maintained by **ActorForge**. Reliability first: every actor in the
portfolio is monitored by an automated nightly self-test, and breakages are
typically fixed the same day.*

# Actor input Schema

## `states` (type: `array`):

2-letter state codes of the physical address, e.g. TX, CA, FL.

## `cities` (type: `array`):

Optional city names, e.g. Dallas, Houston (combine with states).

## `dotNumbers` (type: `array`):

Look up specific registrations by USDOT number (digits only).

## `nameContains` (type: `string`):

Only registrations whose legal or DBA name contains this text, e.g. LOGISTICS, EXPRESS.

## `status` (type: `string`):

USDOT status.

## `operation` (type: `string`):

Carrier operation.

## `entityTypes` (type: `array`):

Only registrations of any of these types. Empty = all.

## `authorizedForHireOnly` (type: `boolean`):

Only for-hire carriers (they haul for others), not private fleets.

## `minPowerUnits` (type: `integer`):

Fleet size floor. 0 = no minimum.

## `maxPowerUnits` (type: `integer`):

Fleet size ceiling. 0 = no maximum.

## `minDrivers` (type: `integer`):

Driver-count floor. 0 = no minimum.

## `addedWithinDays` (type: `integer`):

Only USDOT numbers added in the last N days (new carriers and new authorities). 0 = any date.

## `hazmatOnly` (type: `boolean`):

Only registrations flagged as carrying hazardous materials.

## `cargo` (type: `array`):

Only carriers hauling any of these cargo types. Empty = all.

## `companiesOnly` (type: `boolean`):

Leave out individuals (owner-operators registered under their own name).

## `includeContacts` (type: `boolean`):

Add the phone and e-mail from the census for companies (corporations, partnerships, LLC/INC names). Never output for individuals.

## `sortBy` (type: `string`):

Order of the results.

## `maxItems` (type: `integer`):

Stop after this many registrations. Each one is one charged row.

## Actor input object example

```json
{
  "states": [
    "TX"
  ],
  "cities": [],
  "dotNumbers": [],
  "nameContains": "",
  "status": "active",
  "operation": "any",
  "entityTypes": [],
  "authorizedForHireOnly": false,
  "minPowerUnits": 10,
  "maxPowerUnits": 0,
  "minDrivers": 0,
  "addedWithinDays": 0,
  "hazmatOnly": false,
  "cargo": [],
  "companiesOnly": false,
  "includeContacts": true,
  "sortBy": "newest",
  "maxItems": 20
}
```

# Actor output Schema

## `carriers` (type: `string`):

One row per USDOT registration: DOT/MC numbers, names, status, entity type, operation, address, fleet and drivers, cargo, safety rating, dates and company contacts.

## `summary` (type: `string`):

Carriers delivered, requests made, whether the site refused a request, and billing.

# 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 = {
    "states": [
        "TX"
    ],
    "minPowerUnits": 10,
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("actor-forge/fmcsa-carrier-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 = {
    "states": ["TX"],
    "minPowerUnits": 10,
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("actor-forge/fmcsa-carrier-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 '{
  "states": [
    "TX"
  ],
  "minPowerUnits": 10,
  "maxItems": 20
}' |
apify call actor-forge/fmcsa-carrier-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,actor-forge/fmcsa-carrier-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/T8TKCUspXKAItb5KG/builds/n6aOvDCEUy089oQWv/openapi.json