# FMCSA Broker Financial Security Monitor (Unofficial) (`dromb/fmcsa-broker-financial-security-monitor`) Actor

Monitor official FMCSA BMC-84/BMC-85 broker financial-security filings, recent cancellations, replacement security, and authority-history signals from public DOT data.

- **URL**: https://apify.com/dromb/fmcsa-broker-financial-security-monitor.md
- **Developed by:** [Dmitriy Gyrbu](https://apify.com/dromb) (community)
- **Categories:** 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 security record or signals

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Broker Financial Security Monitor (Unofficial)

Monitor official U.S. FMCSA broker and freight-forwarder financial-security filings with a narrow focus on BMC-84 surety bonds and BMC-85 trust funds.

This Actor uses the U.S. Department of Transportation public Open Data Portal. It does not scrape SAFER, does not require a buyer login, and does not need an API key for normal runs.

### Why this is different

Most FMCSA Actors are broad carrier lookup or lead feeds. This Actor focuses on a specific compliance and counterparty-monitoring workflow:

- current or pending BMC-84 and BMC-85 security filings;
- recent recorded security cancellations;
- whether a different BMC-84 or BMC-85 filing is already on file for the same docket;
- matching same-day FMCSA operating-authority history when present;
- bounded, deterministic source queries with no per-docket network fan-out.

### Quick start

Empty input is safe. It runs active_security with a small result limit.

```
{"mode":"active_security","maxResults":10}
```

Recent cancellation signals:

```
{"mode":"recent_cancellations","maxResults":50,"includeReplacement":true,"includeAuthority":true}
```

Optional docketNumbers and usdotNumbers filters are applied after the bounded primary source query.

### Official sources

R1 uses:

- Motus Insur - All With History for current or pending BMC-84/BMC-85 policies;
- Motus InsHist daily difference for recent cancellation and history events;
- Motus AuthHist daily difference for matching authority-history changes.

The primary query is bounded by maxScan. Replacement and authority correlation are batched. There is no request per broker.

### Critical semantic guard

A BMC-84 or BMC-85 cancellation is not proof of financial failure, insolvency, fraud, default, or any legal conclusion.

financialFailureOrInsolvencyExplicit remains false in this release because R1 does not yet ingest the separate FMCSA public-notice stream that explicitly identifies financial failure or insolvency. The Actor never upgrades a routine cancellation to that claim.

A matching authority-history event is also an observation only. causalAuthorityLinkDetermined remains false and legalOrCreditDecision remains false.

### Output

Depending on mode, rows can include:

- docket and USDOT identifiers;
- BMC form and security instrument type;
- policy number and provider;
- security amount;
- effective and cancellation-effective dates;
- recorded cancellation/history class;
- replacement-security correlation;
- authority-history correlation;
- days until cancellation becomes effective;
- official source and deterministic fingerprint.

### Output example

A current security row can look like:

```
{"docketNumber":"MC55211887","usdotNumber":"5040976","formCode":"84","securityInstrumentType":"BMC-84_SURETY_BOND","policyNumber":"101994946","providerName":"Merchants National Bonding, Inc.","coverageAmountUsd":75000,"effectiveDate":"2026-10-02","signalType":"ACTIVE_BROKER_FINANCIAL_SECURITY","financialFailureOrInsolvencyExplicit":false}
```

A cancellation row can additionally include cancellationEffectiveDate, replacementSecurityOnFile, latestAuthorityEvent, authorityImpactObserved and daysUntilCancellationEffective.

### Network and cost bounds

- Public DOT Socrata API.
- No proxy or browser.
- One request for active_security.
- Up to three requests for recent_cancellations.
- Concurrency 1.
- No per-result or per-docket fan-out.

### Billing

Pay per published result; there is no Actor start fee. Planned tiered result pricing for the public release is: FREE $0.006, BRONZE $0.005, SILVER $0.0045, and GOLD/PLATINUM/DIAMOND $0.004 per published row. Runs that publish no rows do not intentionally emit result charges.

This Actor is unofficial and is not affiliated with FMCSA or the U.S. Department of Transportation.

# Actor input Schema

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

active_security lists current/pending BMC-84/BMC-85 filings. recent_cancellations correlates daily cancellation records with replacement security and same-day authority history.

## `docketNumbers` (type: `array`):

Optional local filter such as MC1481430. No per-docket network fan-out is used.

## `usdotNumbers` (type: `array`):

Optional local USDOT filter.

## `includeReplacement` (type: `boolean`):

For recent cancellations, correlate against the full active/pending BMC-84/BMC-85 dataset.

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

Attach matching records from the official daily Motus AuthHist dataset when present. No causal link is inferred.

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

Maximum rows written to the Dataset.

## `maxScan` (type: `integer`):

Hard bound on the primary FMCSA source query before local filters.

## Actor input object example

```json
{
  "mode": "active_security",
  "includeReplacement": true,
  "includeAuthority": true,
  "maxResults": 10,
  "maxScan": 500
}
```

# Actor output Schema

## `results` (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 = {
    "mode": "active_security"
};

// Run the Actor and wait for it to finish
const run = await client.actor("dromb/fmcsa-broker-financial-security-monitor").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": "active_security" }

# Run the Actor and wait for it to finish
run = client.actor("dromb/fmcsa-broker-financial-security-monitor").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": "active_security"
}' |
apify call dromb/fmcsa-broker-financial-security-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,dromb/fmcsa-broker-financial-security-monitor"
        }
    }
}
```

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/vbBbCibH3y10CdzzZ/builds/zuONrCjijlFv4jTku/openapi.json