# FMCSA New Carrier Authority Scraper (`usta/fmcsa-new-carrier-authority`) Actor

Motor carriers, brokers and freight forwarders newly granted FMCSA operating authority. Pick a window of 1-30 days; get one row per grant with USDOT number, docket number, name, city and state.

- **URL**: https://apify.com/usta/fmcsa-new-carrier-authority.md
- **Developed by:** [US Tech Automations](https://apify.com/usta) (community)
- **Categories:** Business, Lead generation, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$4.00 / 1,000 result rows

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

## This Week's New Trucking Authority Leads

Freight-factoring and trucking-insurance sales reps get this week's newly authorized carriers, with the company name already joined to the grant date, ready to call first.

Every motor carrier, broker and freight forwarder granted new operating
authority by the Federal Motor Carrier Safety Administration in a chosen window
of the last 1 to 30 days. One row per grant, with the USDOT number, the docket
(MC) number, the company name, and the city and state the agency has on file.

### Introduction

A new trucking company cannot legally haul for hire until FMCSA grants it
operating authority. The day that happens, the company needs insurance, a
factoring line, an electronic logging device, and load board access. It is also
the day its record first appears in the agency's public register.

This Actor reads that register live and returns the grants from a recent window.
Pick how many days back to read, optionally narrow to motor carriers, brokers or
freight forwarders, optionally narrow to one state, and set a ceiling on how
many rows the run may return.

Two public datasets published by FMCSA on the US Department of Transportation's
open data portal are used:

- `Motus AuthHist - All With History`, the dated record of authority actions.
  A row marked `GRANTED` is one grant of operating authority on that date.
- `Motus Carrier - All With History`, which supplies the company name, trade
  name, city, state and country for a USDOT number.

The grant history table holds no names, so the two are joined on the USDOT
number. Both datasets are marked `Public Access Level: public` by their
publisher and are refreshed daily.

Nothing is cached and nothing is bundled. Every run reads the agency's portal at
the moment it runs. If the portal cannot be reached, the run reports `UNKNOWN`
with the exact error and returns no rows, rather than serving a stale copy.

### Tutorial

1. Set **Days back** to the size of the window you want. `7` reads today and the
   six days before it. `1` reads today only. The maximum is `30`.
2. Leave **Kind of authority** on `all`, or pick `carrier`, `broker` or
   `freight-forwarder`.
3. Leave **State** empty for the whole country, or enter a two-letter code such
   as `TX`.
4. Set **Maximum rows** to the most rows you are willing to pay for. This is the
   only control on what a run costs.
5. Run it. Results arrive in the default dataset and can be downloaded as JSON,
   CSV or Excel.

Recent volume, read from the register on 14 September 2026: between about 80 and
300 grants a day across the whole country. A seven-day national window is
therefore usually in the range of 1,000 to 1,500 rows, so set **Maximum rows**
deliberately before a wide run.

### Pricing

**$0.004 per row.** There is no start fee, so a run that returns no rows costs
nothing. Every row returned is charged, beginning with the first row.

The cost of any run is capped by **Maximum rows**: 100 rows is $0.40, 1,000 rows
is $4.00. Rows that are refused by your filters are never returned and never
charged. A run that fails or is given bad input returns nothing and charges
nothing.

### Input and output examples

Input:

```json
{
  "daysBack": 7,
  "authorityType": "all",
  "maxItems": 100
}
```

Input, narrowed to brokers newly granted authority in Texas over the last
fortnight:

```json
{
  "daysBack": 14,
  "authorityType": "broker",
  "state": "TX",
  "maxItems": 250
}
```

One output row:

```json
{
  "usdot_number": "3880517",
  "docket_number": "MC82038341",
  "legal_name": "MAKINA TRANSPORT LLC",
  "dba_name": null,
  "authority_type": "Motor Carrier of Property (Except Household Goods)",
  "authority_category": "carrier",
  "authority_status": "Active",
  "action": "GRANTED",
  "grant_date": "2026-09-14",
  "city": "MIAMI",
  "state": "FL",
  "country": "US",
  "attribution": "Published by the Federal Motor Carrier Safety Administration on data.transportation.gov. Public Access Level: public.",
  "source_dataset": "data.transportation.gov/resource/yu5v-wbh6 (Motus AuthHist - All With History)",
  "source_url": "https://data.transportation.gov/resource/yu5v-wbh6.json?$where=usdot_number%20%3D%20%273880517%27%20AND%20...",
  "fetched_at": "2026-09-15T02:54:55Z"
}
```

Every field, in every row:

| Field | What it holds |
| --- | --- |
| `usdot_number` | The USDOT number of the company. |
| `docket_number` | The docket number, such as `MC82038341`. |
| `legal_name` | The company's legal name, as the agency records it. |
| `dba_name` | The trading name, when the agency holds one. Often empty. |
| `authority_type` | The agency's own wording, such as `Broker of Property (Except Household Goods)`. |
| `authority_category` | `carrier`, `broker`, `freight-forwarder`, or `other`. |
| `authority_status` | The status attached to the action, such as `Active`. |
| `action` | Always `GRANTED`. Only grants are returned. |
| `grant_date` | The day authority was granted, as `YYYY-MM-DD`. |
| `city` | The city of the business address on file. |
| `state` | The two-letter state code of the business address. |
| `country` | The country code, such as `US` or `MX`. |
| `attribution` | The publisher credit that travels with the row. |
| `source_dataset` | The dataset the grant was read from. |
| `source_url` | A link to the agency's own API record for this exact grant. |
| `fetched_at` | When the row was read, in UTC. |

Open any row's `source_url` in a browser to see the agency's own record for that
grant. It returns that one record.

### Recommendations

Run it daily with **Days back** set to `2` and dedupe on `usdot_number` plus
`docket_number`. A two-day window overlaps yesterday's run, which covers grants
the agency posts late, and the overlap costs a few cents.

One company can be granted more than one authority on the same day, for example
motor carrier and broker together. Those arrive as separate rows sharing a USDOT
number. Treat `usdot_number` plus `docket_number` plus `authority_type` as the
unique key.

Use `state` when you sell into one territory. Use `authorityType` set to
`broker` if you sell surety bonds, since brokers must file a $75,000 bond, and
`carrier` if you sell insurance, factoring or electronic logging devices.

### Limitations

**No contact details.** Street address, telephone number, mailing address and
postcode are published by the agency but are deliberately never requested and
never returned. Rows carry company name, city, state and country only. If you
need a phone number, look the USDOT number up yourself.

**Some rows have no company name.** A USDOT number can appear in the grant
history before the agency's carrier table holds a record for it. Those rows come
back with `legal_name`, `city` and `state` empty; the USDOT and docket numbers
are still exact. The run report counts how many rows this affected. A row with
no state cannot match a state filter.

**The window is counted in UTC, and the register runs behind it.** Actions are
posted during the US business day, so a run early in the UTC day with **Days
back** set to `1` can correctly return nothing. When a run returns no rows, the
report names the newest day the register actually holds a grant for. Setting
**Days back** to `2` or more avoids this.

**Grants only.** Revocations, suspensions, reinstatements and withdrawals are in
the same source but are not returned.

**The agency's data is the limit of accuracy.** Names, cities and states are
returned as published, without correction. Spelling and capitalisation are the
agency's own.

### FAQ

**Where does this data come from?** The `Motus AuthHist - All With History` and
`Motus Carrier - All With History` datasets published by FMCSA on
`data.transportation.gov`. Every row links to its own record there.

**How fresh is it?** The source is refreshed daily and held grants dated the same
day when this Actor was built. Each row records the moment it was read.

**Does a wide window cost more?** Only through the row count. Set **Maximum
rows** to cap the spend of any run.

**Can it go back further than 30 days?** Not through this input. The source
holds decades of history, but this Actor is built for recent grants.

**Why do two rows share a USDOT number?** The company was granted more than one
kind of authority. Each grant is its own row.

**What happens if the portal is down?** The run reports `UNKNOWN` with the exact
error, returns no rows, and costs nothing.

**Are Mexican and Canadian carriers included?** Yes, where the agency grants them
authority. The `country` field distinguishes them.

### Refunds and support

Refunds: if a run returns zero rows for a valid input, email operations@ustechautomations.com within 7 days and we refund that run. Support: same address, replies within 2 business days.

# Actor input Schema

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

How many days of the register to read, counting back from today (UTC). 1 reads today only; 7 reads today and the six days before it. Maximum 30.

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

Narrow the run to one kind of operating authority, or read every kind.

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

Two-letter state code, such as TX. Matched against the state the agency publishes for the company's business address. Leave empty for every state. A grant whose company record has no state yet cannot match a state filter.

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

Hard ceiling on rows returned, and therefore on the cost of the run. Every row returned is charged, starting at the first row.

## Actor input object example

```json
{
  "daysBack": 7,
  "authorityType": "all",
  "state": "TX",
  "maxItems": 100
}
```

# Actor output Schema

## `grants` (type: `string`):

No description

## `csv` (type: `string`):

No description

## `report` (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 = {
    "daysBack": 7,
    "authorityType": "all",
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("usta/fmcsa-new-carrier-authority").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 = {
    "daysBack": 7,
    "authorityType": "all",
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("usta/fmcsa-new-carrier-authority").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 '{
  "daysBack": 7,
  "authorityType": "all",
  "maxItems": 100
}' |
apify call usta/fmcsa-new-carrier-authority --silent --output-dataset

```

## MCP server setup

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

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/uEcm02DF25boIcW4g/builds/J4ckbzvdVJUuxFQJb/openapi.json