# Fmcsa Carrier Signal Feed (`signalserver/fmcsa-carrier-signal-feed`) Actor

- **URL**: https://apify.com/signalserver/fmcsa-carrier-signal-feed.md
- **Developed by:** [Joep van Acht](https://apify.com/signalserver) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $500.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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## US Motor Carrier Signal Feed (FMCSA)

### What you are looking at

A carrier that just received operating authority has to arrange insurance, factoring and an ELD within days.

### Why it costs you

Miss that window and they are on someone else's paper for years. Most teams reach new entrants weeks late, off a list everyone else already worked, and pay a broker for data that was public the day it happened.

### What this actor does

This actor queries FMCSA's public datasets directly and joins them: the company census (owner officer name, phone, email, fleet size, registration date), operating authority status, and insurance filings including the current insurer and the policy cancellation date. Filter by state, fleet size and registration recency to get a same-week feed of newly authorised carriers. The cancellation date gives you a second buying window on established carriers.

### Start here

Set `registeredSinceDays` to 14, add your states, and run it. Those carriers were authorised this month and most have no insurance filing on record yet.

### Output fields

- `dot_number`
- `docket_number`
- `legal_name`
- `dba_name`
- `signal`
- `owner_first_name`
- `owner_last_name`
- `owner_officer`
- `email`
- `phone`
- `cell_phone`
- `city`
- `state`
- `zip`
- `power_units`
- `truck_units`
- `total_drivers`
- `fleet_band`
- `carrier_operation`
- `registered_date`
- `days_since_registration`
- `authority_common`
- `authority_contract`
- `hauls_property`
- `hauls_household_goods`
- `required_coverage`
- `insurer`
- `insurance_effective`
- `insurance_cancels`
- `days_to_cancellation`
- `insurance_window`
- `has_insurance_on_file`
- `coverage_amount`
- `status_code`

### Measured accuracy

Registry data, not inference: 15/15 on owner name, email, phone, fleet size and registration date in verification runs. Requires no API key of any kind, because the underlying FMCSA datasets are public and free.

### Deploy

```bash
APIFY_PUSH_TOKEN=$APIFY_TOKEN_PERSONAL python3 push_to_apify.py
```

SDK-free by design: plain Apify REST via run env vars. Do not reintroduce the apify/crawlee SDK without pinning every transitive dependency.

# Actor input Schema

## `registeredSinceDays` (type: `integer`):

0 = no recency filter. Set 7-30 for the new-authority feed, which is the high-intent window.

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

Two-letter state codes, e.g. TX, GA, FL. Empty = all states.

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

1 filters out registrations with no trucks. Raise for fleets only.

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

Cap fleet size (e.g. 20 for owner-operators and micro fleets).

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

FMCSA publishes a contact email for most carriers.

## `carrierOperation` (type: `string`):

A = interstate, B = intrastate HM, C = intrastate non-HM. Empty = all.

## `includeAuthority` (type: `boolean`):

Adds docket number, common/contract authority status and the cargo classes the carrier is authorised for.

## `includeInsurance` (type: `boolean`):

Adds insurer, coverage and cancellation date (the renewal window).

## `orderBy` (type: `string`):

add\_date DESC for newest registrations; dot\_number ASC for established carriers.

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

How many carriers to return. Start small to check the filters, then scale.

## `socrataAppToken` (type: `string`):

Not required. Only raises FMCSA rate limits on very large pulls.

## Actor input object example

```json
{
  "registeredSinceDays": 30,
  "states": [
    "TX",
    "GA",
    "FL"
  ],
  "minPowerUnits": 1,
  "requireEmail": true,
  "includeAuthority": true,
  "includeInsurance": true,
  "orderBy": "add_date DESC",
  "maxResults": 500
}
```

# Actor output Schema

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

Every US motor carrier from FMCSA's public data, with the owner's name, phone, email, fleet size, operating authority, current insurer and insurance cancellation date. Filter by state, fleet size and registration recency to get a same-week feed of newly authorised carriers, the highest-intent moment in trucking. Built for freight factoring, trucking insurtech, ELD/TMS vendors and fuel-card programs. Requires no API key: the underlying FMCSA datasets are public and free.

# 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",
        "GA",
        "FL"
    ]
};

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

# Run the Actor and wait for it to finish
run = client.actor("signalserver/fmcsa-carrier-signal-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 '{
  "states": [
    "TX",
    "GA",
    "FL"
  ]
}' |
apify call signalserver/fmcsa-carrier-signal-feed --silent --output-dataset

```

## MCP server setup

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