Home / Your TMS

How FreightScout works with your TMS

Works on McLeod, Aljex, Tai, and any TMS your team logs into today, through a supervised agent that needs no API. The agent logs into the TMS the way a rep would, with a harness around it, and reads and writes there where the brokerage grants access. A native API connection is built during onboarding. It is not live today. McLeod PowerBroker, LoadMaster, Aljex, and Tai stay the system of record. FreightScout is not a McLeod Certified Partner.

Last updated 20 September 2026.

Each named system has its own page: Works with McLeod, Works with Aljex, and Works with Tai. The overlay hub is freight brokerage AI that sits on top of your TMS. How the data is held is on security. Buyer pages for the work itself: check call automation, the platform, and pricing.

How it works today

Today a supervised agent logs into the TMS the way a rep would. A harness sits around that session. Where the brokerage grants access, the agent reads and writes in that TMS. This works where the TMS has no read/write API. It is the path that is live. It is not a native API integration.

What onboarding builds

A native API connection is built during onboarding for the TMS that customer runs. That is the commitment for each new customer. It is not live today, and this page does not give a date. McLeod is the first named system on that path. The same commitment covers Aljex, Tai, and any other TMS your team logs into. FreightScout is not a McLeod Certified Partner.

The work, on the TMS you keep

Check calls, load build, cover, and bill run on top of that record. The result is entered through the supervised agent. Build, Cover, Track, and Bill are live and supervised, including invoicing and collections. Booking the carrier and shipper outreach run supervised by default. A broker can switch either to autopilot, per team and per action. Every action is logged and reversible.

The product pages for those jobs are check call automation, load building from emails and tenders, carrier booking, billing, the platform, and pricing.

Side-by-sides that cite another company's own pages, and the day those pages were read, stay under compare. Those pages are comparisons. This page is how the work sits on the TMS you already run.

Questions people actually ask

Which TMS systems does FreightScout work with?

Works on McLeod, Aljex, Tai, and any TMS your team logs into today, through a supervised agent that needs no API. McLeod PowerBroker, LoadMaster, Aljex, and Tai stay the system of record.

How does FreightScout read and write in a TMS today?

A supervised agent logs into the TMS the way a rep would, with a harness around it, and reads and writes there where the brokerage grants access. That needs no API. It works where the TMS has no read/write API.

Is a native API integration live today?

No. A native API connection is built during onboarding. It is not live today.

Is FreightScout a McLeod Certified Partner?

FreightScout is not a McLeod Certified Partner. This page does not imply a certification or a date for one.

Is there a live Aljex or Tai API integration?

No. There is no live API integration for Aljex or Tai today. A native API connection is built during onboarding for the TMS that customer runs. It is not live today.

Do I have to replace my TMS?

No. The TMS you already run stays the system of record. FreightScout is not a new TMS and it is not a load board.

Is the work supervised?

Yes. Build, Cover, Track, and Bill are live and supervised, including invoicing and collections. Booking the carrier and shipper outreach run supervised by default. A broker can switch either to autopilot, per team and per action. Every action is logged and reversible.