Skip to content

Carrier Packet Checker · Freight & Logistics

Vet every new carrier packet against FMCSA before the first load

Each new carrier setup is checked on FMCSA's public data and your blocked list: authority, out-of-service, insurance on file, name mismatches, shared phones or emails. Ops decides every flag.

Available now $99 one-time · never renewsIncluded in Enterprise
Get this agent See how it works

Free account to start. Buying and running live need a paid plan.

  • Starts from an event in a connected app
  • 2 AI steps
  • About 20 min to set up

Sound familiar?

The job, before and after this agent.

What it feels like today

  • “We set up a carrier with inactive authority and found out after the load moved.”
  • “Double brokers reuse phones and emails from carriers we already blocked.”
  • “Checking every packet by hand on the FMCSA site takes time we don't have.”

What you get with the agent

  • USDOT or MC number read from each new setup row; submissions without one flagged to Slack right away.
  • FMCSA lookup of legal name, operating status, out-of-service, authority, insurance on file and safety rating.
  • Matches against your blocked list on DOT, MC, phone, email or domain, plus name mismatches and your own requirements.
  • Flagged or blocked carriers posted to your carrier ops channel with each issue next to the FMCSA value, for a person to decide.

Before

A new carrier sends a packet Friday afternoon. Someone eyeballs it, skips the FMCSA check, and Monday you learn their authority was inactive.

After

The packet hits your sheet, the FMCSA data is pulled, and ops gets a Slack post: legal name doesn't match the DOT record, phone matches a carrier you blocked.

How it works

The whole workflow, step by step.

Starts on each new row in your carrier setup sheet (for example your carrier packet Google Form's response sheet). AI reads the USDOT / MC number and contact details, then the agent looks the carrier up on FMCSA's public QCMobile API (with your free web key, stored encrypted on the FMCSA connection) and reads your blocked carriers tab. It checks operating status, out-of-service, authority, insurance on file, safety rating, name mismatches and blocked matches, including shared phones and emails, against your requirements. Flagged or blocked carriers are posted to your carrier ops channel in Slack with each issue for a person to decide. It's a one-time check per setup, not ongoing monitoring, and it doesn't read uploaded documents.

  1. TriggerNew carrier setup row
  2. AI stepRead the carrier's details
  3. LogicDOT or MC number given?
    • No DOT / MC:Tell ops it can't be checked
    • Check FMCSA:Look the carrier up on FMCSA
  4. App callTell ops it can't be checked
  5. OutputFlagged: no identifier
  6. App callLook the carrier up on FMCSA
  7. App callRead your blocked carriers list
  8. AI stepCheck the carrier
  9. LogicAnything to flag?
    • Clear:Clear
    • Flag or block:Flag it to carrier ops in Slack
  10. OutputClear
  11. App callFlag it to carrier ops in Slack
  12. OutputFlagged to ops

This is the workflow that opens in your workspace when you set the agent up. Every step can be edited.

  1. Step 1New carrier setup rowStarts a run for each new row in your carrier setup sheet (e.g. the response sheet of your carrier packet Google Form).
  2. Step 2Read the carrier's detailsAI pulls the USDOT and MC numbers, legal name, contact, phone and email from the setup row and builds the FMCSA lookup.
  3. Step 3DOT or MC number given?A submission with no USDOT or MC number can't be checked: ops is told right away. The rest are checked against FMCSA.
  4. Step 4Tell ops it can't be checkedPosts the submission to your carrier ops channel: no USDOT or MC number was given.
  5. Step 5Flagged: no identifierThe run history keeps the submission.
  6. Step 6Look the carrier up on FMCSACalls FMCSA's public QCMobile API for the carrier's registration: legal name, operating status, out-of-service, authority and insurance on file. Your free web key is stored encrypted on the FMCSA connection and added to the request as the webKey parameter.
  7. Step 7Read your blocked carriers listReads your Do-Not-Use tab (blocked carriers with DOT / MC numbers, names, phones or emails).
  8. Step 8Check the carrierAI compares the submission with the FMCSA record and your blocked list: operating status, out-of-service, authority, insurance on file, name mismatches and blocked matches, against your requirements.
  9. Step 9Anything to flag?Flagged or blocked carriers go to ops in Slack; clear ones are recorded in the run history.
  10. Step 10ClearThe run history keeps the FMCSA record and the checks for your onboarding file.
  11. Step 11Flag it to carrier ops in SlackPosts the carrier, the verdict and each issue with the FMCSA value to your carrier ops channel for a person to decide.
  12. Step 12Flagged to opsThe run history keeps the submission, the FMCSA record and the issues.

Example run

What goes in, and what comes out.

Example with fictional data

Comes in

Fictional packet: Red River Haulers LLC, USDOT 3245678, MC-1123456, dispatch email and phone, 53' dry van and reefer.

The agent produces

Operating status, authority and insurance on file pulled from FMCSA; a Slack flag if the legal name differs or the phone matches your blocked tab, with the FMCSA value beside each issue.

What you need

Everything it takes to run it.

About 20 minutes from purchase to live. A checklist above the canvas takes you through each step.

Plan

Included in Enterprise; on other paid plans it's $99 once. Agents run live on paid plans, from Basic ($39/mo).

Your AI key

Connect any of 14 AI providers on your own key. Your provider bills usage directly, at cost; we add no markup.

Apps

Checklist

  • A paid plan (agents run live on paid plans).
  • An AI provider key (Settings → AI Providers).
  • Google Sheets and Slack, connected in Settings → Integrations, and an HTTP / Custom API connection to FMCSA.
  • A free FMCSA QCMobile web key, saved encrypted on the FMCSA connection (API key in the webKey query parameter).

Setup, about 20 minutes

  1. Connect your AI provider. The AI steps run on your own key (OpenAI, Anthropic, Google and more). Add one in Settings → AI Providers.
  2. Connect Google Sheets. Connect the Google account that can open your carrier setup sheet and blocked list.
  3. Connect FMCSA (HTTP / Custom API). Get a free FMCSA web key at mobile.fmcsa.dot.gov/QCDevsite. Then in Settings → Integrations → HTTP / Custom API add a connection named FMCSA: base URL https://mobile.fmcsa.dot.gov/qc/services, authentication “API key in a query parameter”, parameter name webKey, and paste the web key as the API key.
  4. Connect Slack. Connect the Slack workspace your carrier ops team uses.
  5. Pick your carrier setup sheet. Open the trigger “New carrier setup row”, pick your Google account, paste the spreadsheet link and pick the tab.
  6. Pick the FMCSA connection. Open “Look the carrier up on FMCSA” and pick the FMCSA connection (the web key stays in the connection).
  7. Pick your blocked carriers list. Open “Read your blocked carriers list”, pick your Google account, the spreadsheet and the tab.
  8. Write your carrier requirements. Open “Check the carrier” and replace the placeholder with your minimums and red flags.
  9. Pick the Slack channels. Open the two Slack steps and pick your account and carrier ops channel in each. Invite the app to private channels first (/invite @Fluxo Flow).
  10. Test it with Dry Run. Press Dry Run: the agent runs on sample data with no messages sent and nothing written to your apps.
  11. Switch the trigger on. Open the trigger and press “Activate app trigger”: from then on each new setup row is checked.

Is it a fit?

Who it's for, and what it won't do.

Built for

  • Freight brokerages onboarding new carriers
  • Carrier relations and compliance reps
  • Smaller brokers without a vetting service

What it doesn't do

  • It's a one-time check per setup row, not ongoing monitoring like Highway, RMIS or Carrier Assure.
  • It uses FMCSA's public data only: it doesn't read insurance certificates, W-9s or other uploaded documents, or verify bank details.
  • It never approves or rejects a carrier: ops decides on every flag.
  • It doesn't write the result back to your sheet or TMS.

We list the limits up front so you can decide before you buy.

Price

$99 one-time

Per workspace. It never renews.

Available now
  • Included at no extra cost on Enterprise.
  • Buying and running it live need a paid plan, from Basic ($39/mo).
  • Dry Run costs nothing: simulated AI and app calls, nothing sent.
  • AI usage is billed by your own provider, at cost. No AI credits to buy from us.
Get this agent See how it works

One-time agent purchases aren't covered by the 30-day money-back guarantee. Refund policy

FAQ

Questions about Carrier Packet Checker.

Does it approve carriers?

Never. It flags issues and your ops team decides. It uses FMCSA public data only and doesn't read insurance certificates, W-9s or bank details.

Is this ongoing monitoring?

No. It's a one-time check per setup row: a consistent first gate at onboarding, not continuous monitoring. It doesn't write results back to your sheet or TMS.

How hard is setup?

About 20 minutes: connect Google Sheets and Slack, create a free FMCSA web key and save it on an HTTP connection, pick your blocked list, write your requirements and run a Dry Run.

What does it cost?

The FMCSA data is free. The agent is a one-time unlock that never renews; live runs need a paid plan and your own AI key, and Dry Run is free.

Where do I get an FMCSA web key?

It's free: sign in at mobile.fmcsa.dot.gov/QCDevsite with Login.gov and create a web key.

Does it keep monitoring carriers after onboarding?

No. It's a one-time check per setup row, not ongoing monitoring like Highway or RMIS.

Is this a subscription?

No. Carrier Packet Checker is a one-time purchase of $99 per workspace and never renews. The Enterprise plan includes it at no extra cost. Running it live needs a paid plan (from Basic ($39/mo)), and your AI provider bills you directly for usage.

Can I test it before it touches real data?

Yes. Once it's set up in your workspace, Dry Run plays every step on sample data with simulated AI and app calls: nothing is sent and nothing in your apps changes. Switch the trigger on only when you're happy.

Put Carrier Packet Checker to work.

Free account, no credit card. Your Agents page opens with Carrier Packet Checker ready to buy and set up, then Dry Run it before it goes live.

Get this agent See how it works