# FMCSA Insurance Cancellation Leads (Trucking, No API Key) (`intenal_builds/fmcsa-insurance-cancellation-leads`) Actor

Trucking companies whose FMCSA-filed liability (BIPD), cargo or bond insurance is cancelling or just cancelled, from the new Motus system. Enriched with phone, email, officers, fleet size and a replacement-policy check. Official DOT open data, no key.

- **URL**: https://apify.com/intenal_builds/fmcsa-insurance-cancellation-leads.md
- **Developed by:** [Jaydan Eaton](https://apify.com/intenal_builds) (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 $4.00 / 1,000 lead 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 Insurance Cancellation Leads – Trucking (Motus, No API Key)

Find **trucking companies whose FMCSA-filed insurance is cancelling or just cancelled**: auto liability (BIPD), cargo, or broker bonds. Every lead is enriched with the carrier's **phone, cell, email, officers, address, fleet size, drivers and cargo types**, plus a check for whether a **replacement policy is already on file**.

Built on FMCSA's new **Motus** registration datasets. FMCSA's legacy L\&I insurance files (`InsHist`, `ActPendInsur`) were frozen on 05/14/2026 and are no longer updated, so tools built on them miss every cancellation filed since. This actor reads the live Motus feeds.

No signup, no API key, no scraping of SAFER pages.

**Who it's for**

- **Commercial truck insurance agents:** carriers with a BIPD cancellation and no replacement on file have days to get covered or lose operating authority. Call them first.
- **Freight brokers & shippers:** vet carriers before tendering loads; drop anyone whose liability is lapsing.
- **Factoring companies & lenders:** monitor clients for coverage gaps.
- **Compliance services, BOC-3 / permit agents:** reach carriers at risk of authority revocation.

### How it works

1. Queries **Motus InsHist – All With History** (`3uet-3z4i`) for filings whose cancellation effective date falls in your window (default: last 14 days to next 30 days).
2. Joins each USDOT to the **Company Census File** (`az4n-8mr2`) for contact and fleet data.
3. Optionally checks **Motus Insur – All With History** (`c5y8-a4uz`) for a newer active filing of the same type, and flags `replacementPolicyOnFile`.

### Input

| Field | Default | Notes |
|---|---|---|
| `daysBack` / `daysAhead` | 14 / 30 | Cancellation effective-date window |
| `cancellationReasons` | `["CANCEL"]` | Add `TERM/REPL` for carriers that just switched insurers |
| `insuranceTypes` | `["BIPD"]` | `BIPD`, `CARGO`, `SURETY`, `TRUST FUND` |
| `states` | all | Physical-address states, e.g. `["TX","AR","OK"]` |
| `minPowerUnits` / `maxPowerUnits` | none | Fleet-size filter |
| `checkReplacement` | true | Flag replacement filings |
| `onlyWithoutReplacement` | false | Keep only true coverage gaps |
| `requireContact` | false | Require phone or email |
| `includeBrokersAndForwarders` | true | Drop FF dockets / BMC-84/85 when false |
| `maxResults` | 100 | Up to 10,000 |

Example: small Texas/Arkansas/Oklahoma fleets losing liability coverage with nothing new on file:

```json
{
  "daysBack": 30,
  "daysAhead": 30,
  "states": ["TX", "AR", "OK"],
  "minPowerUnits": 2,
  "onlyWithoutReplacement": true,
  "requireContact": true,
  "maxResults": 200
}
```

### Output (one row per cancelled filing)

`usdotNumber`, `docketNumber`, `legalName`, `dbaName`, `cancellationReason`, `insuranceType`, `insuranceFormCode`, `insurerName`, `policyNumber`, `coverageMaxAmount`, `policyEffectiveDate`, `cancellationEffectiveDate`, `daysUntilCancellation`, `replacementPolicyOnFile`, `replacementInsurer`, `replacementEffectiveDate`, `phone`, `cellPhone`, `email`, `companyOfficer1`, `companyOfficer2`, `street`, `city`, `state`, `zip`, `powerUnits`, `trucks`, `totalDrivers`, `carrierOperation`, `hazmat`, `cargoCarried`, `censusStatus`, `safetyRating`, `mcs150Date`, `inCensus`, `saferSnapshotUrl`, `source`.

From a real run (Oct 2026): a default run found 1,423 BIPD cancellation filings in the window; the first 100 leads all matched a census record with phone and email, and 6 of 100 already had a replacement policy on file. A filtered TX/AR/OK run (2+ trucks, no replacement, contact required) returned leads such as a 10-truck Houston carrier and a 4-truck McGehee, AR farm hauler.

### Notes and limits

- `replacementPolicyOnFile` is a best-effort check against Motus active filings only; always confirm on the carrier's SAFER / L\&I page before acting.
- Census contact fields are what the carrier reported on its MCS-150; some are stale.
- Follow TCPA, CAN-SPAM and Do-Not-Call rules when contacting carriers.

### Compliance

- Uses only official, public US DOT open-data endpoints (`data.transportation.gov` Socrata SODA API), anonymously, with no key.
- Data is public FMCSA registration and insurance-filing information.
- Requests are throttled to about 1 per second, back off on 429/5xx, and send a declared User-Agent.

### More from Intenal_Builds

- [SAM.gov Federal Contract Opportunities Tracker](https://apify.com/intenal_builds/federal-contract-opportunities-tracker)
- [USASpending Federal Awards Tracker](https://apify.com/intenal_builds/usaspending-federal-awards-tracker)
- [SEC Form D Funding Tracker](https://apify.com/intenal_builds/sec-form-d-funding-tracker)
- [US Federal Lobbying Disclosure Tracker](https://apify.com/intenal_builds/federal-lobbying-disclosure-tracker)

# Actor input Schema

## `daysBack` (type: `integer`):

Include cancellations that took effect up to this many days ago.

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

Include upcoming cancellations effective within this many days (insurers file cancellation notices ahead of the effective date).

## `cancellationReasons` (type: `array`):

CANCEL = the policy is being cancelled (hottest leads). TERM/REPL = the carrier replaced the policy (recent switchers).

## `insuranceTypes` (type: `array`):

Which FMCSA insurance filings to include.

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

Optional. Two-letter physical-address states, e.g. TX, AR, OK. Empty = all states.

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

Optional. Minimum trucks/tractors on the carrier's census record.

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

Optional. Maximum power units (e.g. 10 for small fleets).

## `checkReplacement` (type: `boolean`):

Look up the carrier's active Motus filings and flag whether a newer policy of the same type is already on file.

## `onlyWithoutReplacement` (type: `boolean`):

Keep only carriers with no newer active filing of the same type (true coverage gaps).

## `requireContact` (type: `boolean`):

Skip carriers with no phone, cell phone or email on the census record.

## `includeBrokersAndForwarders` (type: `boolean`):

When false, drops FF dockets and BMC-84/85 broker bond filings.

## `sortOrder` (type: `string`):

Order by cancellation effective date.

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

Stop after this many leads.

## `userAgent` (type: `string`):

Optional contact string sent in the User-Agent header.

## Actor input object example

```json
{
  "daysBack": 14,
  "daysAhead": 30,
  "cancellationReasons": [
    "CANCEL"
  ],
  "insuranceTypes": [
    "BIPD"
  ],
  "checkReplacement": true,
  "onlyWithoutReplacement": false,
  "requireContact": false,
  "includeBrokersAndForwarders": true,
  "sortOrder": "latest_first",
  "maxResults": 100
}
```

# Actor output Schema

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

One item per cancelled or cancelling FMCSA insurance filing.

# 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("intenal_builds/fmcsa-insurance-cancellation-leads").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("intenal_builds/fmcsa-insurance-cancellation-leads").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 intenal_builds/fmcsa-insurance-cancellation-leads --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,intenal_builds/fmcsa-insurance-cancellation-leads"
        }
    }
}
```

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/5HplywS1kU3WYtTGp/builds/FwmzOQhZxmtnFnNTL/openapi.json