US FMCSA Newly Authorized Trucking & Fleet Insurance Leads

Actor: newapi21-fmcsa-new-trucking-authorities
Production code: NEWAPI21
Version: 1.0.0 (Actor source version 1.0)
Source: U.S. Department of Transportation / FMCSA public Motus operating authority and Company Census records
Target Store pricing: Pay per event, $0.005 per unique output Dataset record, $5 per 1,000 results (configure and verify on the Apify Publication tab)

Discover newly granted and currently active FMCSA operating authorities, filtered by state, carrier category and the documented number of power units. Export a ready-to-map Apify Dataset as JSON or CSV for Clay, n8n or a lawful CRM enrichment workflow.

Verification warning: An active FMCSA authority is not proof that an insurance policy provides adequate coverage, that filings are sufficient for a particular customer or route, that a business is looking for insurance, or that the business is ready to purchase. This Actor does not evaluate insurance compliance or outreach eligibility. No automated contact or messaging is performed.

Quick start

Default input (start/end omitted intentionally):

{
  "states": ["TX", "FL"],
  "carrierType": "motor_carrier",
  "authorityTypes": [],
  "minPowerUnits": 1,
  "maxResults": 20,
  "maxCostUsd": 0.1,
  "pageSize": 100,
  "maxSourceRecords": 3000
}

Date-filtered example:

{
  "startDate": "2026-10-20",
  "endDate": "2026-10-22",
  "states": ["TX", "FL"],
  "carrierType": "motor_carrier",
  "minPowerUnits": 1,
  "maxResults": 100,
  "maxCostUsd": 0.5
}

When dates are omitted, the end date is yesterday UTC, and the start date is six days earlier. This avoids confusing in-flight data updates with completed daily authority events. Filter dates are FMCSA Granted authority-event dates, never the Actor's first-observation date, a company's formation date or an insurance filing date. Results depend on what the official source published by the time of the run.

Input parameters

Field	Purpose
startDate, endDate	Optional inclusive UTC Grant event date range in YYYY-MM-DD
states	Two-letter physical-business state codes (default ["TX","FL"])
carrierType	motor_carrier, broker, freight_forwarder or all; default motor carriers
authorityTypes	Exact optional Motus op_auth_type names to narrow type
minPowerUnits	Minimum non-null FMCSA Census power unit count (default 1)
maxResults	Maximum unique authority identities emitted per run (1 to 1000)
maxCostUsd	Cap on result event charges ($0.005 each; zero emits no rows)
pageSize	Official history API page size, 10–500
maxSourceRecords	Limit on eligible history pages; report explicitly indicates capped scans

Pending authority is not a new grant. The Actor deliberately requires a history row with reason = Granted, op_auth_status = Active and a matching current Active Carrier authority. It excludes Pending, Initial Status, Published to FMCSA Register, Reinstated, withdrawn and inactive rows. The source's legacy common/contract consolidation reinstatement events are not treated as new grants.

Official FMCSA datasets and mapping

Purpose	Dataset	ID
Historical authority change events, including Grant date	Motus AuthHist - All With History	yu5v-wbh6
Current authority status, legal name and physical business address	Motus Carrier - All With History	inys-ebih
Fleet, driver counts, cargo classification and fallback company phone	Company Census File	az4n-8mr2
Optional daily difference verification; not used as historical range source	Motus AuthHist daily	dm5j-zc6c
Optional daily difference verification	Motus Carrier daily	nakq-58th

Live metadata verified 23 Oct 2026: Motus datasets refreshed that day and Census last refreshed 22 Oct 2026. Metadata and actual row updates may change.

Legacy warning: AuthHist - All With History dataset ID 9mw4-x3tu (and old Carrier All With History) stopped receiving new source records in May 2026. They are not used for newly granted authority decisions.

Matching and deduplication: Historical event -> current authority via normalized (docket_number, USDOT number, exact operating-authority type), then Census via exact USDOT. Under legacy authority rules one docket may have several distinct authority types, so deduplicating on USDOT alone would be wrong. Missing or conflicting current authority states are rejected. All optional values come from official fields and remain null if not found. mc_number is populated only when the actual docket uses the MC prefix; the general docket_number field preserves FF and MX identifiers.

Temporal semantics: authorization_date comes from status_change_date on a real Granted Motus history event, formatted as ISO date. observed_at is the Actor's UTC reading time, NOT the grant date. A newly granted authority is not necessarily a newly formed company or first-time carrier.

Output Dataset (JSON and CSV)

Every row is one unique verified USDOT + docket + authority type. Apify supplies native JSON and CSV downloads. Structured fields:

• dot_number, docket_number, mc_number (null for FF/MX)
• legal_name, dba_name, business_phone, physical_address
• power_units_count, drivers_count, cargo_carried
• authority_type, authorization_date, authority_status
• source_url (official filtered FMCSA source), observed_at (UTC)

For Clay, import the default Apify Dataset CSV and map dot_number and docket_number as text identifiers. For n8n, use the Apify Dataset items endpoint as JSON with dot_number, docket_number and authority_type as a combined record key. This Actor itself does not email, call, scrape personal social profiles, send cold outreach or make contact.

Run's default key-value store also includes RUN_SUMMARY (counts, source IDs, filtering, cost estimate, source scan status) and CHECKPOINT (source offset and already seen identities, for interrupted-restart recovery within the same run's KV store). If a source limit is hit, do not interpret output as an exhaustive scan.

Cost controls and publication pricing

Expected Apify pricing configuration: Pay per event (PPE), with exactly one event: apify-default-dataset-item at $0.005, primary event, no actor-start fee, and no second custom record event. The SDK's Actor.pushData() automatically charges that configured synthetic event. The Actor never calls Actor.charge() for the same record.

The configured input maxCostUsd caps these result event charges, not all independent platform resource costs. No proxy is required. Verify the Console pricing before public release.

Unique returned authorities	Customer result event charge
1	$0.005
100	$0.50
1,000	$5.00

Per Apify PPE's published economics, the developer receives 80% of gross event revenue before underlying platform costs. At 1,000 paid records, $5 billed, $4 before platform costs; net profit requires the actual Actor platform usage measurement. Publishing and billing are not complete until the Apify Console confirms the price and publication visibility.

Reliability

• Socrata API v2 endpoints over HTTPS; one authenticated X-App-Token can be supplied from optional environment variable SOCRATA_APP_TOKEN (never hardcode or log it).
• Date-filtered history pages with explicit deterministic $order, $limit, $offset.
• Current authority / Census joins in bounded batches (45 docket identities per lookup).
• HTTP request timeouts (12 s), bounded 3 attempts for transient network/429/server errors, Retry-After capped backoff.
• Request budget 160, record cap, output cap, event price cap and approximately 245 s processing deadline.
• Checkpoint per history page; emitted default Dataset IDs are loaded on restarts to avoid duplicate output billing. No cross-run state guarantee or cross-run atomic transaction is claimed.
• No automatic outreach; source business telephone and address are published FMCSA fields, not evidence of consent for any specific marketing channel.

Run locally

cd /opt/NEWAPI/NEWAPI21
npm ci
npm test
mkdir -p storage/key_value_stores/default
cp .actor/INPUT.json storage/key_value_stores/default/INPUT.json
npm start

The working tree is scoped to /opt/NEWAPI/NEWAPI21; it does not modify any other API/NEWAPI project.

Quality acceptance

Automated unit scenarios include active Granted, Pending, Reinstated, duplicated dockets, absent business phone, null-value behavior, state/fleet filters, 429 retry, pricing cap and resume/replay avoidance. Integration tests use genuine FMCSA records for Texas and Florida; official data contents and source freshness are time-dependent.

Use responsibly: Check actual registration and applicable insurance requirements directly with FMCSA and a qualified insurance professional before relying on an authority for underwriting or solicitation. Follow the laws and contact-channel rules that apply to the use of public contact records.