# Freight Load Vet: FMCSA Carrier, Broker + OFAC (`veteran_zythem/freight-load-vet`) Actor

Vet a load before you tender it: FMCSA carrier authority + safety BASICs, broker authority and an OFAC name screen, rolled into one TENDER / HOLD / REJECT verdict with plain reasons and cited sources. For brokers, dispatchers, factoring and AI freight agents.

- **URL**: https://apify.com/veteran_zythem/freight-load-vet.md
- **Developed by:** [Craig Nkonge](https://apify.com/veteran_zythem) (community)
- **Categories:** Automation, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $50.00 / 1,000 load vetteds

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

## Freight Load Vet: FMCSA carrier + broker + OFAC in one verdict

Before you tender a load, run one check instead of four. For each load this Actor pulls the **live FMCSA record** for the carrier (operating authority) plus FMCSA's **current monthly SMS BASIC safety results**, checks the **broker's FMCSA authority**, screens the legal name against **OFAC sanctions lists**, and returns one verdict:

- **TENDER**: authority active, nothing alarming in the public record
- **HOLD**: something needs a human look (e.g. a BASIC over the intervention threshold, a REVIEW-level name match, missing data)
- **REJECT**: not authorized to operate, broker authority inactive, or a sanctions hit

Every verdict comes with **plain-English reasons** and the **sources** it used (FMCSA QCMobile, OFAC list date). No invented "fraud score": the verdict follows only from public federal fields.

### Who it's for

- **Freight brokers and dispatchers** vetting a carrier before booking
- **Carriers** checking that an unfamiliar broker is real and authorized
- **Factoring companies and shippers** checking counterparties in bulk
- **AI freight agents** that need a yes/no gate in a workflow (works through the Apify MCP server)

### Input

Give a list of loads. Each load needs at least one of `dot`, `mc` or `brokerMc`:

```json
{
  "loads": [
    { "reference": "LOAD-1001", "dot": "44110", "brokerMc": "MC-121058", "name": "Example Trucking LLC" },
    { "reference": "LOAD-1002", "mc": "MC-515000" }
  ]
}
```

Quick mode: pass `"dotNumbers": ["44110", "2233"]` to vet carriers by USDOT only.

### Output (one row per load)

| Field | Meaning |
|---|---|
| `verdict` | TENDER / HOLD / REJECT |
| `reasons` | Why, in plain English |
| `carrierAuthority` | Legal name, operating status, authority, safety rating, fleet size |
| `safetyDataAsOf` | When FMCSA published the safety (SMS BASIC) data behind this verdict |
| `safetyDataStale` | `true` if that data is more than 75 days old, or the shelf returned `DATA_QUALITY_HOLD_SAFETY_DATA_STALE`. A stale feed is a reason to HOLD, not a carrier problem |
| `holdBasis` | `data_quality` or `carrier_risk` when the shelf says why it held. `data_quality` means the **data** is stale or incomplete. It is **not** a finding against the carrier. Re-check once fresh FMCSA data is out |
| `holdNote` | Plain-English note on data-quality holds |
| `partial` | `true` if a requested section timed out. That section shows `status: "timeout"` and the verdict is at least HOLD (never TENDER; a REJECT stays REJECT). `false` when every requested section answered |
| `sections` | Status of each section: `authority`, `basics`, `broker`, `ofac` = `ok`, `timeout` or `skipped` (skipped = not requested) |
| `safetyDataFormat` | `sms_monthly` (current) or `legacy_qcmobile` (old 2017 feed) |
| `safetyCarrierGroup` | `passenger` or `property`. FMCSA doesn't publish percentiles or threshold alerts for property carriers (FAST Act), so for most freight carriers only acute/critical violations can flag |
| `safetyFlags` | Safety flags behind the verdict, e.g. `ACUTE_CRITICAL_DRIVER_FITNESS`, `BASICS_DATA_STALE` |
| `carrierBasics` | Full SMS BASIC detail per category (percentile where public, measure, acute/critical, alert, inspections with violations) |
| `brokerAuthority` | Broker's authority status (when `brokerMc` is given) |
| `ofac` | Sanctions screen of `name` (when given) |
| `sources` | Data sources and dates |
| `reference` | Your load ID, echoed back |

### Example output (real run)

Real output from a run on 2026-10-18 for USDOT 44110 (trimmed):

```json
{
  "reference": "ONA-0.1.9-44110",
  "dot": "44110",
  "verdict": "HOLD",
  "reasons": [
    "ACUTE_CRITICAL_DRIVER_FITNESS"
  ],
  "holdBasis": "carrier_risk",
  "holdNote": null,
  "safetyDataFound": true,
  "safetyDataAsOf": "2026-10-13T07:05:22.000Z",
  "safetyDataStale": false,
  "safetyDataFormat": "sms_monthly",
  "safetyCarrierGroup": "passenger",
  "safetyFlags": [
    "ACUTE_CRITICAL_DRIVER_FITNESS"
  ],
  "safetyDataSource": "FMCSA SMS monthly results",
  "carrierAuthority": {
    "carrier": {
      "legal_name": "GREYHOUND LINES INC",
      "dot": 44110,
      "allowed_to_operate": "Y",
      "status_code": "A"
    },
    "authority": {
      "common": "A",
      "contract": "A",
      "broker": "I"
    },
    "safety": {
      "rating": "S"
    }
  },
  "carrierBasics": {
    "carrier_group": "passenger",
    "as_of": "2026-10-13T07:05:22.000Z",
    "stale": false,
    "basics": [
      {
        "basic": "Driver Fitness",
        "percentile": 57,
        "percentile_public": true,
        "acute_critical_violation": true,
        "basic_alert": true,
        "inspections_with_violation": 7
      }
    ],
    "…": "other BASICs trimmed"
  },
  "ofac": {
    "skipped": true,
    "reason": "no legal name provided"
  },
  "error": null
}
```

This HOLD has `holdBasis: "carrier_risk"` because FMCSA's current data shows an acute/critical Driver Fitness violation.

**Data-quality holds.** If FMCSA's monthly safety data is stale, the verdict is `HOLD` with reason `DATA_QUALITY_HOLD_SAFETY_DATA_STALE`, `holdBasis: "data_quality"` and `safetyDataStale: true`. This is a data-quality hold, not a carrier risk. It says nothing bad about the carrier.

A carrier with no SMS data this month comes back with `safetyDataFound: false`. That's common for small or new carriers, and it is **not** a clearance.

### Pricing

**$0.05 per load vetted.** That's one charge for authority + BASICs + broker + OFAC together.
**Invalid or failed loads are free.** Set a max cost per run and the Actor stops cleanly when it is reached.

### Important

A decision aid built on public FMCSA and OFAC data, not a guarantee against fraud or double brokering. FMCSA data can lag real-world changes; confirm insurance directly for high-value loads.

A section that times out returns status "timeout" with partial:true and a HOLD verdict (never TENDER; a REJECT stays REJECT). Full price applies when carrier authority (broker, for a broker-only pack) is delivered; if that core section times out, or every section does, the call fails with 503 before payment settles.

Built by **Ni Biashara LLC** (Texas). The same check is available pay-per-call to agents over x402 at [agents.nibiashara.biz](https://agents.nibiashara.biz/shelf/load-vet-pack).

# Actor input Schema

## `loads` (type: `array`):

One object per load. Fields: dot (carrier USDOT), mc (carrier MC/docket), brokerMc (broker MC/docket), name (legal name to OFAC-screen), reference (your load ID, echoed back). Give at least one of dot, mc or brokerMc.

## `dotNumbers` (type: `array`):

Just carrier USDOT numbers. Each one is vetted as its own load (authority + BASICs).

## `maxItems` (type: `integer`):

Safety cap on how many loads this run vets.

## Actor input object example

```json
{
  "loads": [
    {
      "reference": "LOAD-1001",
      "dot": "44110",
      "brokerMc": "MC-121058",
      "name": "Example Trucking LLC"
    }
  ],
  "maxItems": 500
}
```

# Actor output Schema

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

All vetted loads in the default dataset (overview view).

# 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 = {
    "loads": [
        {
            "reference": "LOAD-1001",
            "dot": "44110",
            "brokerMc": "MC-121058",
            "name": "Example Trucking LLC"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("veteran_zythem/freight-load-vet").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 = { "loads": [{
            "reference": "LOAD-1001",
            "dot": "44110",
            "brokerMc": "MC-121058",
            "name": "Example Trucking LLC",
        }] }

# Run the Actor and wait for it to finish
run = client.actor("veteran_zythem/freight-load-vet").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 '{
  "loads": [
    {
      "reference": "LOAD-1001",
      "dot": "44110",
      "brokerMc": "MC-121058",
      "name": "Example Trucking LLC"
    }
  ]
}' |
apify call veteran_zythem/freight-load-vet --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,veteran_zythem/freight-load-vet"
        }
    }
}
```

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/YuWH4OGFrfZhgQBqV/builds/3YpTHDzAe50wWpvb5/openapi.json