# FMCSA MCS-150 Due Date Lead Finder (`quartz_apple_dnx/fmcsa-mcs150-due-date-lead-finder`) Actor

Find public FMCSA carrier records whose scheduled MCS-150 biennial filing deadline is overdue or approaching, with contact and fleet filters.

- **URL**: https://apify.com/quartz\_apple\_dnx/fmcsa-mcs150-due-date-lead-finder.md
- **Developed by:** [Austin DeMoss](https://apify.com/quartz_apple_dnx) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$10.00 / 1,000 qualified fmcsa carrier leads

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 MCS-150 Due Date Lead Finder

Find public FMCSA carrier records whose scheduled MCS-150 biennial filing deadline is approaching or has recently passed, then filter them into outreach-ready business lead rows.

This Actor uses the official FMCSA Company Census File published on the U.S. Department of Transportation open-data portal. It does not scrape SAFER pages, use a browser, require an FMCSA login, or invent a proprietary compliance score.

### What makes this different

Generic FMCSA carrier exporters give you a large census dump. This Actor applies the official biennial filing schedule to each USDOT number and compares that schedule with the published MCS-150 update date. The result is a smaller list centered on a concrete timing trigger.

FMCSA's schedule is deterministic:

- the last USDOT digit determines the filing month (1=January through 9=September, 0=October);
- the next-to-last digit determines odd/even filing years;
- the filing deadline is the last day of the required month;
- an MCS-150/MCS-150C update completed during the 12 months immediately preceding the biennial deadline satisfies that cycle.

### Example input

```json
{
  "daysOverdue": 30,
  "daysAhead": 90,
  "states": ["TX", "OK"],
  "activeOnly": true,
  "requirePhone": true,
  "excludeAlreadySatisfied": true,
  "minPowerUnits": 1,
  "maxResults": 1000
}
```

### Output

Each row includes the public carrier identity/contact/fleet fields plus:

- `scheduledDueDate` — the last day of the carrier's scheduled filing month;
- `daysUntilDue` — negative when the scheduled deadline has passed;
- `mcs150Date` — latest MCS-150 date published in the census row, when present;
- `satisfactionWindowStart` — first day of the 12-month period immediately preceding the scheduled deadline;
- `latestUpdateQualifies` — whether that published date falls in the satisfaction window;
- `filingStatus` and `qualificationReason` — transparent schedule-derived labels;
- source dataset and exact query provenance.

### Important interpretation limits

This output is a **schedule-derived lead list**, not an FMCSA enforcement determination, legal opinion, or guarantee that a carrier is noncompliant. Public data can lag or contain errors. Verify important records before acting on them.

The MCS-150 biennial update itself is free through FMCSA. This Actor charges for filtering, calculation, and structured lead delivery—not for filing with FMCSA.

If you use contact information for outreach, you are responsible for following applicable marketing, calling, texting, and email rules.

### Source

FMCSA Company Census File: `az4n-8mr2` on data.transportation.gov.

# Actor input Schema

## `asOfDate` (type: `string`):

Optional YYYY-MM-DD anchor date. Leave blank to use today's UTC date.

## `daysOverdue` (type: `integer`):

Look this many days backward from the as-of date.

## `daysAhead` (type: `integer`):

Look this many days forward from the as-of date.

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

Optional two-letter physical-state filters such as TX, CA, FL.

## `activeOnly` (type: `boolean`):

Require FMCSA census status code A.

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

Only query records with a published business phone or cell phone.

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

Only query records with a published email address.

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

Optional minimum published fleet power units.

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

Optional maximum published fleet power units.

## `excludeAlreadySatisfied` (type: `boolean`):

Exclude rows whose published MCS-150 update date falls within the 12 months immediately preceding the scheduled deadline.

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

Maximum output rows to save and charge.

## `maxScanRows` (type: `integer`):

Hard cap on public FMCSA census rows examined in one run.

## `batchSize` (type: `integer`):

Rows requested per public-data API page.

## `timeoutSecs` (type: `integer`):

Maximum seconds for each public-data API request.

## Actor input object example

```json
{
  "daysOverdue": 30,
  "daysAhead": 90,
  "activeOnly": true,
  "requirePhone": false,
  "requireEmail": false,
  "excludeAlreadySatisfied": true,
  "maxResults": 1000,
  "maxScanRows": 100000,
  "batchSize": 2000,
  "timeoutSecs": 30
}
```

# Actor output Schema

## `leads` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("quartz_apple_dnx/fmcsa-mcs150-due-date-lead-finder").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("quartz_apple_dnx/fmcsa-mcs150-due-date-lead-finder").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 '{}' |
apify call quartz_apple_dnx/fmcsa-mcs150-due-date-lead-finder --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,quartz_apple_dnx/fmcsa-mcs150-due-date-lead-finder"
        }
    }
}
```

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/Z9wGYHnnlFuLvlcDk/builds/85ufxfevDf1oTZBbd/openapi.json