Freigent Network

The connected freight network

Your software.
An entire freight network.

Connect your TMS to a shared network where brokers and carriers find each other across participating platforms. Nobody leaves the software they already use.

Become a design partner How it works
Early partner program · In development

01 · The problem

Freight software does not talk to itself. Your customers pay for it.

  1. i.A broker's load lives in one system. The carrier who should haul it works in another.
  2. ii.So the load goes out by email, phone and portal, and comes back the same way.
  3. iii.Every software provider builds its own integrations, one counterparty at a time.
  4. iv.Customers on competing platforms cannot work together without someone re-keying the load.

02 · How it will work

Connect once. Reach across platforms.

i.

Connect your software

One standard API, or drop-in components. Your customers connect their accounts to the network through you.

ii.

Brokers choose what to share

A broker publishes the loads it picks, to its own approved carriers or wider. Nothing is shared by default.

iii.

Carriers respond where they work

Loads appear inside the carrier's own TMS. Interest and offers flow back into the broker's system.

A hosted sandbox is open for software providers to build and test against. Real loads move with the first pilot.

03 · Why providers join

Keep your software. Keep your customers. Expand their reach.

i.

Your product does more

Your customers reach counterparties on other platforms without leaving your screens.

ii.

Your customers stay yours

Your brand, your relationships, your contracts. We do not use your customers' data to sell to them.

iii.

No network to build alone

Skip building one-off integrations with every counterparty your customers trade with.

iv.

Bring your own AI

Your agents can take part under the same rules as people, and every action says which it was.

04 · Built for interoperability

Four ways in. Pick per feature.

i.

Hosted pages

Customers whose software is not connected yet can still see loads and respond.

No code
ii.

Drop-in components

Load search, publishing and an offer inbox that sit inside your app, in your brand.

Inside your app
iii.

API and SDK

Plain HTTPS and JSON from any language, with a TypeScript SDK first. Build your own screens.

Your own UI
iv.

Agent kit

Instructions your AI coding agent follows to build the integration and test it until it passes.

Built by your agent

Start with our pieces. Replace any of them with your own later. You stay compatible either way.

05 · Trust and control

Same rules for everyone. Including us.

How the network is designed to work.

  • Companies control what they shareLoads are private until a broker chooses who sees them.
  • No automatic exposurePrivate loads, rates and customer details are never shown wider than their owner allows.
  • Verified companiesOrganizations are checked against their USDOT and MC records before they can publish or make offers.
  • People and software are labeledEvery action records whether a person or an AI agent took it, and the other side can see which.
  • One set of rulesPublished, and the same for every provider, including Freigent's own software. Network data stays walled off from Freigent's own TMS and sales.
  • Tested before going liveEvery integration passes the same compatibility tests before it can reach real customers. Ours too.

06 · Early partner program

Help shape the network.

We are working with a small number of broker and carrier software providers to build the first connections, starting with trading relationships their customers already have.

  1. i.A seat on protocol changes, written into the partner agreement
  2. ii.First access to the developer sandbox
  3. iii.Pilot with us on real lanes your customers already run
Software category

We use this only to follow up about the partner program.