# FMCSA New MC Authority Leads With Insurance & BOC-3 Status (`hamsmoothie/fmcsa-new-authority-status`) Actor

New FMCSA operating authorities (MC applications, Register publications, grants) and insurance suspensions, joined with insurance on file vs required, insurer, BOC-3 agent, phone and email. Filter by state, event and insurance status. $15 per 1,000.

- **URL**: https://apify.com/hamsmoothie/fmcsa-new-authority-status.md
- **Developed by:** [Maybe Quark](https://apify.com/hamsmoothie) (community)
- **Categories:** Other, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$15.00 / 1,000 fmcsa authority events

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 MC Authority Leads With Insurance & BOC-3 Status

**FMCSA New Authority With Insurance Status** returns trucking companies, brokers and freight forwarders that just **applied for**, were **published for**, or were **granted** FMCSA operating authority (MC, FF and MX dockets), each joined with what the carrier still needs: **liability insurance required vs on file**, the **insurer and policy** once filed, **cargo insurance**, the **broker bond** (BMC-84/85) and the **BOC-3 process agent**. Contact details (phone, cell, email, officer, address) and fleet size come from the FMCSA census. It also returns the other side of the cycle: authorities **suspended for an insurance or BOC-3 cancellation**, voluntary suspensions and **reinstatements**.

Most new-authority lists stop at "here is a new MC number". This one tells you which new carriers **still have no insurance on file**, which is the exact moment a carrier buys its first policy.

### Who it is for

- **Commercial truck insurance agents**: `insurance: "missing"` returns pending authorities with no BIPD filing yet. FMCSA will not grant the authority until a BMC-91/91X is filed, so these carriers need a policy now.
- **BOC-3 process agent and compliance services**: pending authorities with `boc3OnFile: false`.
- **Factoring companies, fuel cards, load boards, ELD and dispatch services**: `granted` events are carriers that can start hauling this week, with the insurer already known.
- **Agents who keep their book**: `insurance_suspended` events are carriers whose insurance was cancelled and whose authority is now inactive.
- **Agent and automation builders**: flat, typed, dated rows. Schedule a daily run with `onlyNewSinceLastRun` and pipe the result into a CRM, a dialer queue or an AI agent.

### What an event is

| eventType | what happened at FMCSA |
|---|---|
| `applied` | New operating authority application on file (status Pending). |
| `published` | The application was published in the FMCSA Register; the protest period is running and the carrier must file insurance and a BOC-3 before the grant. |
| `granted` | The authority became Active. |
| `insurance_suspended` | Involuntary suspension or inactivation because the insurance on file was cancelled. |
| `boc3_suspended` | Suspension because the BOC-3 process agent filing was cancelled. |
| `voluntary_suspended` | The carrier asked to suspend its authority. |
| `reinstated` | The authority came back to Active (for example, insurance restored). |
| `inactivated`, `other` | Other inactivations, administrative corrections and withdrawals. |

About 1,700 applications, 1,600 publications and 1,300 grants a week nationwide (October 2026), plus around 500 insurance suspensions.

### Input

All fields are optional. This example returns this week's Texas applicants and published carriers that still have no insurance on file:

```json
{
  "days": 7,
  "eventTypes": ["applied", "published"],
  "state": "TX",
  "insurance": "missing",
  "maxResults": 500
}
```

- `days`: events from the last N days (default 7, up to 90).
- `changedSince`: `YYYY-MM-DD`; only events on or after that date. Overrides `days`. Pass the date of your last run for an incremental pull.
- `eventTypes`: default `applied`, `published`, `granted` (new authority). Add `insurance_suspended`, `reinstated` and the rest for the full cycle.
- `state`: two-letter state of the business address, e.g. `TX`. Empty means all states.
- `authorityType`: `any`, `property`, `household`, `passenger`, `broker` or `forwarder`.
- `insurance`: `missing` (a required insurance or bond filing is not on file), `onFile` or `any`.
- `onlyNewSinceLastRun`: skip events this actor already returned to your account (daily diff mode).
- `maxResults`: stop after this many rows, newest first (default 100).

### Output

One row per authority event, newest first. Sample rows (run 2026-10-24):

| eventType | eventDate | docketNumber | legalName | city | state | insuranceRequiredUsd | insuranceOnFile | insurer | boc3OnFile | missingForAuthority |
|---|---|---|---|---|---|---:|---|---|---|---|
| published | 2026-10-22 | MC99915675 | CV PRESTIGE TRANSPORT GROUP CORP | MIRAMAR | FL | 750000 | false | | false | BIPD liability insurance (BMC-91/91X); BOC-3 process agent |
| applied | 2026-10-23 | MC97518057 | 506 TRUCKING LLC | Bethel | PA | 750000 | false | | false | BIPD liability insurance (BMC-91/91X); BOC-3 process agent |
| granted | 2026-10-23 | MC99620684 | TFM Trucking LLC | Kent | WA | 750000 | true | UNITED FINANCIAL CASUALTY COMPANY | true | |

Full example row:

```json
{
  "eventType": "granted",
  "eventDate": "2026-10-23",
  "reason": "Granted",
  "docketNumber": "MC58544747",
  "usdotNumber": "9386014",
  "authorityType": "Motor Carrier of Property (Except Household Goods)",
  "authorityStatusNow": "Active",
  "legalName": "ANGELINA TRANSPORT LOGISTICS LLC",
  "dbaName": null,
  "companyOfficer": "SHEENA PERSAUD",
  "phone": "9084050605",
  "cellPhone": null,
  "email": "princess_christine162000@yahoo.com",
  "street": "544 WOODEN AVE",
  "city": "SOUTH PLAINFIELD",
  "state": "NJ",
  "zip": "07080",
  "usdotAddedDate": "2026-10-07",
  "powerUnits": 2,
  "drivers": null,
  "hazmat": false,
  "insuranceRequiredUsd": 750000,
  "insuranceOnFileUsd": 750000,
  "insuranceOnFile": true,
  "insurer": "DRIVE NEW JERSEY INSURANCE COMPANY",
  "insurancePolicyNo": "CA881588514",
  "insuranceForm": "BMC-91X",
  "insuranceEffectiveDate": "2026-10-22",
  "cargoInsurer": null,
  "bondSurety": null,
  "boc3OnFile": true,
  "processAgent": "Evilsizor Process Servers Inc",
  "missingForAuthority": null,
  "url": "https://safer.fmcsa.dot.gov/query.asp?searchtype=ANY&query_type=queryCarrierSnapshot&query_param=USDOT&query_string=9386014"
}
```

- `authorityStatusNow`: the authority's status today, which can differ from the event (an application published last week may be granted by now).
- `insuranceRequiredUsd` / `insuranceOnFileUsd`: the BIPD minimum FMCSA requires for this authority and the amount on file. `missingForAuthority` lists every required filing that is not on file yet.
- `phone`, `cellPhone`, `email`, `companyOfficer`, `powerUnits`: from the FMCSA census (MCS-150). A USDOT number created in the last few days may not be in the census yet; those rows still carry the business phone from the authority record.
- `url`: the carrier's FMCSA SAFER snapshot.

### For agent builders

Run daily with `"onlyNewSinceLastRun": true`, or pass `changedSince` from your last run. `docketNumber` plus `eventType` plus `eventDate` is a stable key. A good agent prompt: take `published` rows with `insuranceOnFile: false`, group by state, and draft one short note per carrier that names the docket number and the filings it still needs.

### Pricing

Pay per result: each row is one billable result at **$0.015** ($15 per 1,000), below the usual $20 per 1,000 for plain new-authority lists, with the insurance and BOC-3 status included. The default run returns at most 100 rows ($1.50). Apify's free plan includes a monthly platform credit that covers a few hundred rows, so you can judge the data first. Set a maximum charge on the run for a hard ceiling.

### Limits

- Source: FMCSA's public Motus registration datasets (authority history, authority records, insurance filings, BOC-3 filings) and the Company Census File, published by the U.S. DOT and refreshed daily. Events usually appear one day after FMCSA records them.
- Authorities registered under the legacy system can hold several authority types on one docket; the actor matches the authority type of each event.
- Insurance filing amounts on an authority record can lag a cancellation by a few days. For suspensions, trust the event and `authorityStatusNow`.
- Emails and phones are what the carrier filed with FMCSA. You are responsible for how you contact these businesses, including the TCPA, CAN-SPAM and the National Do Not Call Registry.
- Public record. This actor is not affiliated with or endorsed by FMCSA or the U.S. DOT.

### FAQ

**How is this different from a new carrier (new USDOT) list?** A USDOT number is only a registration. Operating authority (an MC number) is what lets a carrier haul for hire across state lines, and it cannot go active without insurance on file. That is why the authority events, with the insurance status, are the buying signal. For plain new USDOT registrations, see the companion FMCSA new carrier registrations actor by the same publisher.

**Can I get only carriers that still need insurance?** Yes: `"insurance": "missing"` with `eventTypes` `applied` and `published`.

**Why does one carrier appear more than once?** One application produces an `applied`, a `published` and a `granted` event over a few weeks. Keep one `eventType`, or use `onlyNewSinceLastRun`.

# Actor input Schema

## `days` (type: `integer`):

Authority events whose status change date is in the last N days. Ignored when Changed since is set.

## `changedSince` (type: `string`):

Only events on or after this date, e.g. 2026-10-20. Overrides Days. Use the date of your last run for an incremental pull.

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

Which authority events to return. Default: new authority (applied, published, granted).

## `state` (type: `string`):

Only carriers whose business address is in this state, e.g. TX. Empty = all states.

## `authorityType` (type: `string`):

Limit to one kind of operating authority.

## `insurance` (type: `string`):

missing = required insurance or bond not on file yet (the carrier still needs a policy); onFile = all required filings present; any = both.

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

Skip events already returned by an earlier run of this actor in your account (daily diff mode).

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

Stop after this many rows (newest first). Each row is one billable result.

## Actor input object example

```json
{
  "days": 7,
  "changedSince": "",
  "eventTypes": [
    "applied",
    "published",
    "granted"
  ],
  "state": "",
  "authorityType": "any",
  "insurance": "any",
  "onlyNewSinceLastRun": false,
  "maxResults": 100
}
```

# Actor output Schema

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

FMCSA operating-authority events with insurance, BOC-3 and contact details, newest first.

# 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("hamsmoothie/fmcsa-new-authority-status").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("hamsmoothie/fmcsa-new-authority-status").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 hamsmoothie/fmcsa-new-authority-status --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,hamsmoothie/fmcsa-new-authority-status"
        }
    }
}
```

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/TMQkGqbTIYFlcbz12/builds/d9bvZ6FwBeYEKsEqS/openapi.json