# FMCSA New Carriers and Authority Status Changes Feed (`longlever/fmcsa-carriers-feed`) Actor

Newly registered US trucking companies and operating authority status changes (granted, revoked, suspended, reinstated) from official FMCSA open data, with filters and an only-new-since-last-run mode for daily lead feeds.

- **URL**: https://apify.com/longlever/fmcsa-carriers-feed.md
- **Developed by:** [Todd Handler](https://apify.com/longlever) (community)
- **Categories:** Lead generation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 new carrier returneds

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 New Carriers and Authority Status Changes Feed

Get newly registered US trucking companies and every operating authority change (granted, revoked, suspended, reinstated) from official FMCSA open data, in one clean schema. Schedule it daily and each run returns **only what is new since the last run**.

- **New carriers.** Companies added to the FMCSA Company Census File, with name, address, phone, email, officers, fleet size, drivers, cargo, operation type and MC/MX/FF dockets.
- **Authority status changes.** Each status event from FMCSA's Motus authority history: applications, grants, insurance and BOC-3 suspensions, revocations, reinstatements and more, each with the carrier's details attached. Most feeds sell only new registrations; this one also tracks what happens to authorities afterwards.
- **Only new since last run.** No diffing on your side. Late FMCSA postings are caught, and nothing is returned twice.
- **Filters that matter for lead lists.** State, fleet size, operation type, authority status, USDOT status, entity type, hazmat, must have email or phone, event type and authority type.
- **Official source, no scraping of SAFER.** Reads the public data.transportation.gov API. Dataset IDs are looked up by name on every run, so a dataset replacement by FMCSA does not break your schedule.
- **Cheap and predictable.** $3 per 1,000 new carriers and $4 per 1,000 status changes.

### Who uses it

- **Truck insurance agents** reaching new authorities before their first renewal, and carriers whose insurance was just cancelled
- **Factoring companies and fuel card providers** looking for brand-new fleets
- **ELD, dispatch, compliance and TMS vendors** onboarding new carriers
- **Freight brokers** vetting carriers and watching for revocations and suspensions on carriers they use
- **Lenders and equipment dealers** tracking small fleets in their region

### Quick start

1. Choose **What to return**: New carriers, Authority status changes, or Both.
2. Add filters, for example **States** `TX` and **Maximum power units** `5`.
3. Click **Start**. The first run returns the last 7 days (change **Look back days** for more).
4. Create a daily **Schedule** in Apify Console. Each run then returns only new rows.
5. Send results to Google Sheets, a CRM, Slack, a webhook, Make or n8n with Apify integrations.

For a one-off pull, turn off **Only new since last run**. The run then returns the whole look-back window, newest first, and saves nothing.

### What counts as new

- **New carriers:** records whose Census `ADD_DATE` falls in the window. FMCSA posts most records one to three days after that date, so a daily run usually shows the previous few days' registrations. FMCSA also uses `ADD_DATE` when a record is reactivated, so a few rows may be older companies coming back.
- **Status changes:** rows in FMCSA's "Motus AuthHist - All With History" dataset whose status change date falls in the window. One carrier can have several events in a day (for example applied, then published).
- Each run re-reads the last 10 days before its previous high-water mark and skips anything already returned, so records FMCSA posts late are still delivered once.
- Saved progress is tied to your filters. Changing a filter starts a fresh baseline. Set **State key** to give it a fixed name.

### Filters

| Filter | Applies to | What it does |
|---|---|---|
| States | Both | Physical address state, for example `TX`, `CA` |
| Minimum / maximum power units | Both | Fleet size. `maxPowerUnits` 5 targets owner-operators and small fleets |
| Operation type | Both | Interstate, intrastate hazmat, intrastate non-hazmat |
| Operating authority | New carriers | Active MC/MX/FF docket, inactive docket, or no docket |
| USDOT record status | Both | Active, inactive, pending |
| Entity type | Both | Carrier, broker, freight forwarder, shipper and more |
| Hazmat only, must have email, must have phone | Both | |
| Event types | Status changes | Applied, published, granted, suspended, revoked, inactivated, reinstated and more |
| Authority type | Status changes | Property carrier, household goods, passengers, broker, freight forwarder |
| Date added on or after | Both | Hard start date |
| Max rows per feed per run | Both | Caps each feed. Held-back rows come in the next run |

Carrier filters on status changes use the carrier's Census record. Events for carriers with no Census match are dropped when a carrier filter is set.

### Output

One row per new carrier or status change. `record_type` tells them apart. Example status change (values are illustrative):

```json
{
  "record_type": "status_change",
  "usdot_number": "4123456",
  "docket_number": "MC1234567",
  "authority_type": "Motor Carrier of Property (Except Household Goods)",
  "authority_category": "carrier_property",
  "new_status": "inactive",
  "event_type": "suspended",
  "reason": "Involuntary Suspension - insurance cancellation effective; no active insurance meeting minimum coverage on file",
  "status_change_date": "2026-10-21",
  "carrier_found": true,
  "legal_name": "EXAMPLE TRUCKING LLC",
  "dba_name": null,
  "carrier_status": "active",
  "operation_type": "interstate",
  "power_units": 3,
  "drivers": 3,
  "phone": "5125550100",
  "email": "dispatch@example.com",
  "street": "100 MAIN ST",
  "city": "AUSTIN",
  "state": "TX",
  "zip": "78701",
  "authority_dockets": ["MC1234567"],
  "fmcsa_url": "https://safer.fmcsa.dot.gov/query.asp?searchtype=ANY&query_type=queryCarrierSnapshot&query_param=USDOT&query_string=4123456",
  "fetched_at": "2026-10-22T13:00:00Z"
}
```

New-carrier rows have the same carrier fields plus `added_date`, `mcs150_date`, `entity_types`, `operation_classes`, `cargo_types`, `company_officers`, `trucks`, `buses`, `cdl_drivers`, mailing address and `authority_status`. The event fields are null on those rows.

**Field notes**

- `event_type` is derived from FMCSA's reason text. The original is kept in `reason` (email addresses FMCSA sometimes embeds there are replaced with `[email]`).
- `authority_status` on new carriers summarizes the dockets on the Census record. On a status change, `new_status` is the authority's status after the event.
- `carrier_status` is the USDOT record status, separate from operating authority.
- Each run writes a `SUMMARY` record to the key-value store: the dataset IDs it used and how it found them, the query window, and rows fetched, already seen, matched and pushed per feed.

### Pricing

Pay per event. You pay only for rows delivered.

| Event | Price |
|---|---|
| New carrier returned | $0.003 ($3 per 1,000) |
| Status change returned | $0.004 ($4 per 1,000) |

Nationwide, FMCSA adds roughly 400 to 600 carriers and 1,000 to 1,500 authority events on a typical weekday, fewer on weekends. A daily nationwide new-carrier feed costs about $1.50 a day. A one-state, small-fleet feed of both kinds costs cents a day. Set a maximum cost per run in the run options and the Actor stops cleanly at that limit; anything held back comes in the next run.

### Compliance: contacting carriers

This data is public, but **how you use it is your responsibility.**

- **Phone and text:** the TCPA and the FCC's rules restrict autodialed and prerecorded calls and texts, especially to cell phones, which many owner-operator numbers are. Check the National Do Not Call Registry and your state's rules before calling or texting.
- **Email:** commercial email must follow CAN-SPAM: accurate headers and subject lines, a valid physical postal address, and a working opt-out honored within 10 business days.
- Some states add their own telemarketing and privacy rules. Get legal advice for your use case.
- The Actor returns what FMCSA publishes. Verify a carrier's current status on FMCSA SAFER before relying on it for a business decision.

### For AI agents

- **Input:** `mode` (`new_carriers`, `status_changes`, `both`), `onlyNewSinceLastRun`, `lookbackDays`, and the filters above (`states`, `minPowerUnits`, `maxPowerUnits`, `operationTypes`, `authorityStatuses`, `carrierStatuses`, `entityTypes`, `eventTypes`, `authorityCategories`, `requireEmail`, `requirePhone`, `hazmatOnly`), plus `maxItems`.
- **Output:** flat rows; `record_type` is `new_carrier` or `status_change`. The `SUMMARY` key-value record reports what was read.
- **Cost:** $0.003 per new carrier, $0.004 per status change. Use `maxItems` and filters to keep runs small.

### Source and limits

- Data: FMCSA "Company Census File" and "Motus AuthHist - All With History" on data.transportation.gov, published by the Federal Motor Carrier Safety Administration. This Actor is not affiliated with or endorsed by FMCSA or the US DOT.
- The Actor uses the public Socrata API, rate-limited and retried on temporary errors. An optional free Socrata app token raises the rate limit for very large pulls.
- FMCSA retired the legacy "Carrier - All With History" dataset in May 2026 when it moved registrations to Motus. This Actor uses the Motus datasets and finds them by name each run.

### Support

Open an issue on the Actor page. Issues are answered within one business day.

# Actor input Schema

## `mode` (type: `string`):

New carriers: companies newly added to the FMCSA Company Census File. Status changes: operating authority events (granted, revoked, suspended, reinstated and more) from FMCSA's Motus authority history. Both: one run, both feeds.

## `onlyNewSinceLastRun` (type: `boolean`):

Return only carriers and events this Actor has not returned before for the same filters (schedule it daily). The first run returns the last "Look back days". Turn off for a one-off pull of the whole look-back window, newest first.

## `lookbackDays` (type: `integer`):

First run, or every run when "Only new since last run" is off: how many days back to read, by date added (new carriers) or status change date (events).

## `addedSince` (type: `string`):

Optional hard start date (YYYY-MM-DD). Nothing dated earlier is returned, whatever the look-back.

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

Two-letter state codes, for example TX, CA, FL. Empty means all states.

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

Trucks, tractors, buses and other power units the carrier reported.

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

For example 5 to target owner-operators and small fleets.

## `operationTypes` (type: `array`):

Empty means any.

## `authorityStatuses` (type: `array`):

Active: holds an active MC, MX or FF docket. Inactive: has a docket, none active. None: no docket (private or intrastate carriers). Empty means any. New-carrier feed only.

## `carrierStatuses` (type: `array`):

Status of the USDOT record in the Census File. Empty means any.

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

Keep entities registered as any of these. Empty means any.

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

Keep only entities flagged as hazardous materials carriers or shippers.

## `requireEmail` (type: `boolean`):

Drop records with no email on file.

## `requirePhone` (type: `boolean`):

Drop records with no phone or cell phone on file.

## `eventTypes` (type: `array`):

Status-change feed only. Empty means all.

## `authorityCategories` (type: `array`):

Status-change feed only. Empty means all.

## `includeCarrierDetails` (type: `boolean`):

Look up each event's carrier in the Census File for name, address, phone, email and fleet size. Always on when a carrier filter is set.

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

0 means no limit. Applies to each feed separately in Both mode. In only-new mode, rows held back by this limit come in the next run.

## `stateKey` (type: `string`):

Optional name for the saved progress. By default it is derived from your filters, so changing a filter starts a fresh baseline.

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

Free token from data.transportation.gov that raises the API rate limit for large pulls. Not needed for daily runs.

## Actor input object example

```json
{
  "mode": "new_carriers",
  "onlyNewSinceLastRun": true,
  "lookbackDays": 7,
  "hazmatOnly": false,
  "requireEmail": false,
  "requirePhone": false,
  "includeCarrierDetails": true,
  "maxItems": 50
}
```

# Actor output Schema

## `newCarriers` (type: `string`):

Carrier rows in the new-carrier column layout. Status-change rows appear here too in Both mode; filter on record_type.

## `statusChanges` (type: `string`):

Authority status-change rows in the event column layout.

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

Datasets used (resolved by name at run time), query window, rows fetched, matched and pushed per feed, and any errors.

# 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 = {
    "mode": "new_carriers",
    "lookbackDays": 7,
    "maxItems": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("longlever/fmcsa-carriers-feed").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 = {
    "mode": "new_carriers",
    "lookbackDays": 7,
    "maxItems": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("longlever/fmcsa-carriers-feed").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 '{
  "mode": "new_carriers",
  "lookbackDays": 7,
  "maxItems": 50
}' |
apify call longlever/fmcsa-carriers-feed --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,longlever/fmcsa-carriers-feed"
        }
    }
}
```

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/ItCjiFSVkzHtwxgvM/builds/VeVI5hgIsIL3adDUu/openapi.json