# New Trucking Companies (FMCSA) & Carrier Leads (`digital_influx/us-trucking-companies`) Actor

New US trucking companies from the official FMCSA census, updated daily: USDOT number, phone, email, officers, power units, drivers, operation, hazmat and cargo types. Filter by state, fleet size and cargo. Look up USDOT numbers.

- **URL**: https://apify.com/digital_influx/us-trucking-companies.md
- **Developed by:** [Bruno Petrelli](https://apify.com/digital_influx) (community)
- **Categories:** Lead generation, Business, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.00 / 1,000 carrier saveds

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

## New Trucking Companies (FMCSA) & Carrier Leads

**Every new US trucking company the day it registers with the FMCSA**, from the official Company Census File, updated daily:

- the USDOT number, legal and DBA name, and the date it was added;
- phone, cell phone, fax and email;
- the company officers;
- power units, trucks, drivers and CDL drivers;
- interstate or intrastate operation, hazmat, cargo types, classification and MC docket numbers.

No account, no API key, no proxies: the data comes from data.transportation.gov, the open data portal of the US Department of Transportation.

### Who uses it

- **Truck insurance agents and brokers:** a new carrier needs liability and cargo insurance before it can run.
- **Freight factoring, fuel cards, ELD and dispatch services:** new owner-operators and small fleets, with phone and email.
- **Truck and trailer dealers, driver schools, compliance services:** new fleets by state, size and cargo.
- **Freight brokers:** new carriers for their lanes, with interstate operation and cargo types.

### What you get

One record per carrier (USDOT number):

| Field | Example |
|---|---|
| `dotNumber`, `legalName`, `dbaName` | 9211336, RLEGACY EMPIRE LLC |
| `addedDate`, `lastUpdateDate` | When the USDOT number was added; the last MCS-150 update |
| `status`, `operation`, `classification` | `active`, `interstate` (or `intrastate`, `intrastate-hazmat`), \["AUTHORIZED FOR HIRE"] |
| `hazmat`, `cargoTypes` | `false`, \["General freight"] |
| `powerUnits`, `trucks`, `buses`, `drivers`, `cdlDrivers` | 2, 0, 0, 2, 0 |
| `officers` | \["NATHANIEL VILLANUEVA", "NORA ROMERO"] |
| `phone`, `cellPhone`, `fax`, `email` | 346-941-0265, rlegacyempirellc@icloud.com |
| `street`, `city`, `state`, `zip`, `country`, `mailingAddress` | 2522 COVERED WAGON DR, CROSBY, TX, 77532 |
| `dockets` | MC and MX docket numbers, where the carrier has operating authority |
| `sharedContact` | `true` when the email or phone is also on 2 or more other carriers of the run: a registration or compliance service's, not the carrier's own |
| `saferUrl`, `sourceUrl`, `retrievedAt` | The carrier's SAFER snapshot, the dataset and when it was read |
| `change` | With *Only new*: `new` or `updated` |

The **OUTPUT** record has the totals, the count by state and by operation, and the attribution.

### Input

New carriers in Texas this week:

```json
{
  "addedWithinDays": 7,
  "states": ["TX"],
  "maxResults": 50
}
```

New interstate carriers with an email in the last week, every state (the census runs two or three days behind, so a window under 4 days can be empty):

```json
{
  "addedWithinDays": 7,
  "operations": ["interstate"],
  "onlyWithEmail": true
}
```

New hazmat and refrigerated carriers with at least 2 trucks this month:

```json
{
  "addedWithinDays": 30,
  "hazmatOnly": true,
  "cargoTypes": ["coldfood", "chem"],
  "minPowerUnits": 2
}
```

Look up carriers by USDOT number:

```json
{
  "dotNumbers": ["9211336", "9130661"]
}
```

| Field | What it does |
|---|---|
| `addedWithinDays` | Carriers added in the last N days (30 by default, up to 365). |
| `states` | 2-letter codes of the physical address. |
| `operations` | Interstate, intrastate hazmat, intrastate. |
| `cargoTypes` | MCS-150 cargo classifications (general freight, household goods, refrigerated food, chemicals...). |
| `minPowerUnits`, `maxPowerUnits` | Fleet size. |
| `hazmatOnly`, `onlyWithEmail`, `onlyWithPhone` | Narrow the list. |
| `includeInactive` | Also inactive and pending USDOT numbers (only active by default). |
| `dotNumbers` | Look up these carriers whatever their date of addition. |
| `maxResults` | Carriers saved, newest first (1,000 by default). |
| `onlyNew` + `memoryName` | For daily runs: only the carriers earlier runs of the same search did not save, or whose status, phone, email or fleet changed. The memory lives in a key-value store named `us-trucking-companies-state`. |
| `appToken` | Free Socrata app token, optional. |

### How much it costs

Pay per event: **only for the carriers saved**. Measured on 2026-10-02: 13,489 carriers were added in September 2026 (about 400 to 600 each weekday), all with a phone and all but one with an email; a week of Texas is about 135 carriers, read in under 2 seconds.

### Use it from AI agents (MCP)

Claude, ChatGPT, Cursor and any other MCP client can run this Actor as a tool: add `https://mcp.apify.com?tools=digital_influx/us-trucking-companies` as a remote MCP server and sign in with your Apify account. It is also one of the tools of US & UK Public Records MCP (`digital_influx/public-records-mcp`), by the same author, made for agents.

### Good to know

- **The census is published daily, two or three days behind:** the newest additions are usually from two days ago.
- **Shared contacts:** many new carriers register through a filing or compliance service, whose email and phone end up on many records. `sharedContact` flags them within the run.
- **Fleet numbers are what the carrier declared** on its MCS-150 form when it registered; many new carriers declare 0 to 2 power units.
- **Personal data:** many owner-operators use a personal email and phone. The FMCSA publishes them, but they are personal data: follow the TCPA and CAN-SPAM rules (and state laws) for calls, texts and emails.
- **Requests:** one a second, as the portal's robots.txt asks. Without a token the portal shares a request limit per IP address; if a run reports a refused request, add a free Socrata app token.

### Source and attribution

Federal Motor Carrier Safety Administration (FMCSA), "Company Census File", published on data.transportation.gov (dataset az4n-8mr2), U.S. Department of Transportation open data. The FMCSA does not endorse this Actor or the uses of its results.

# Actor input Schema

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

Carriers added to the FMCSA census in the last N days. The census is published daily, two or three days behind.

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

2-letter codes of the physical address, e.g. TX, CA. Empty = every state.

## `operations` (type: `array`):

Interstate carriers, intrastate hazmat carriers or intrastate carriers. Empty = all.

## `cargoTypes` (type: `array`):

Keep carriers that haul one of these (MCS-150 cargo classifications). Empty = all.

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

Trucks and tractors the carrier declares. Many new carriers declare 1 or 2.

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

Only carriers with at most this many power units (trucks and tractors), e.g. 5 for small fleets.

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

Save only carriers that haul hazardous materials.

## `onlyWithEmail` (type: `boolean`):

Save only carriers that have an email address in the FMCSA census.

## `onlyWithPhone` (type: `boolean`):

Save only carriers that have a phone number in the FMCSA census.

## `includeInactive` (type: `boolean`):

By default only active USDOT numbers are kept.

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

Look up these carriers whatever their date of addition (up to 2,000).

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

Carriers saved in this run, newest first. You also never pay more than the spending limit you set for the run.

## `onlyNew` (type: `boolean`):

Save only carriers that earlier runs of this same search did not save, or whose status, phone, email or fleet changed since. Schedule it daily. The memory lives in a key-value store named "us-trucking-companies-state" in your account.

## `memoryName` (type: `string`):

By default each search has its own memory. Give a name to share one memory between tasks, or a new name to start over.

## `appToken` (type: `string`):

Without a token, the portal shares a request limit per IP address. A free app token from any Socrata portal gives you your own limit. Only needed if a run reports a refused request.

## Actor input object example

```json
{
  "addedWithinDays": 7,
  "states": [
    "TX"
  ],
  "hazmatOnly": false,
  "onlyWithEmail": false,
  "onlyWithPhone": false,
  "includeInactive": false,
  "maxResults": 50,
  "onlyNew": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

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

No description

# 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 = {
    "addedWithinDays": 7,
    "states": [
        "TX"
    ],
    "maxResults": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("digital_influx/us-trucking-companies").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 = {
    "addedWithinDays": 7,
    "states": ["TX"],
    "maxResults": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("digital_influx/us-trucking-companies").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 '{
  "addedWithinDays": 7,
  "states": [
    "TX"
  ],
  "maxResults": 50
}' |
apify call digital_influx/us-trucking-companies --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,digital_influx/us-trucking-companies"
        }
    }
}
```

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/QD7xXzVcgrBIFLLhh/builds/wYokeQjAtn4WqyHTo/openapi.json