freight-load-scanner

Scan DAT/Truckstop load boards and vet carriers via FMCSA SAFER API.

Updated Mar 4, 2026
One-click install
npx skills add https://github.com/wasay1200/freight-broker-ai --skill freight-load-scanner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: freight-load-scanner
Source: https://github.com/wasay1200/freight-broker-ai/tree/main/skills/freight-load-scanner
Command: npx skills add https://github.com/wasay1200/freight-broker-ai --skill freight-load-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Automates the discovery of freight loads and the verification of carriers, reducing manual searching and risk in lane-specific sourcing.

Core Features & Use Cases

  • Load-board scanning to find matches on DAT/Truckstop.
  • Carrier vetting via FMCSA SAFER API (or SAFER scraping when API keys are unavailable).
  • SMS-style result summaries for brokers and on-demand monitoring.

Quick Start

Scan DAT for loads from Los Angeles, CA to New York, NY and vet MC123456 using SAFER.

Frequently Asked Questions about freight-load-scanner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I vet a carrier using FMCSA SAFER data for load board compliance checks?

Carrier vetting via FMCSA SAFER queries the free API using an MC number to verify compliance. When API keys are unavailable, SAFER web scraping provides carrier verification as a fallback to reduce manual sourcing risk.

How do I scan DAT and Truckstop load boards for lane-specific freight loads?

Scanning DAT and Truckstop load boards requires live API access using DAT_CLIENT_ID and DAT_CLIENT_SECRET to search freight loads matching broker criteria. A sample-data fallback enables lane-specific monitoring without active credentials.

Can I use the FMCSA SAFER API to automate carrier compliance checks during load scanning?

Automating carrier compliance checks pairs load-board scanning with FMCSA SAFER API verification using FMCSA_WEB_KEY. This automatically vets carriers found on DAT or Truckstop during lane-specific load searches to reduce manual verification effort.

Do I need DAT API credentials to find freight loads, or is sample data available?

Live DAT load-board scanning requires DAT_CLIENT_ID and DAT_CLIENT_SECRET credentials for real-time freight matches. A sample-data fallback supports testing and monitoring lane-specific load searches without active API authentication.

What is the best way to format load board and carrier vetting results for SMS delivery?

Formatting load board and carrier vetting results for SMS delivery condenses lane-specific freight matches and FMCSA SAFER compliance data into concise text summaries. This enables brokers to receive automated load monitoring alerts directly.

Why does carrier vetting fall back to SAFER scraping when the FMCSA API is unavailable?

Carrier vetting falls back to SAFER scraping when FMCSA_WEB_KEY is unavailable to ensure compliance checks still function. This maintains carrier verification during load scanning when free API access fails or lacks authentication.