API First

Take the whole platform, or one service

Nothing here is UI-only. Rating, tender, tracking, document retrieval and audit are all available over the API — so you can run our interface, wire ours into yours, or port a single service into the system you already have without replacing anything.

One freight API across LTL, parcel and truckload: a rating API, a tracking API, tender and documents, plus MCP for assistants. Call it from your own TMS, ERP or customer portal.

Talk to us about the API MCP & agents

Three ways to consume it

Most platforms make you take all of it or none of it. The point of building API-first is that you do not have to.

Run it in ours

Use the platform as your TMS, or under your own brand. The interface is a client of the same API everyone else calls.

Wire it into yours

Keep your own front end, your own ERP, your own customer portal. Call the API for the parts you want and render them wherever your users already work.

Port one service

Take rating on its own. Or audit on its own. Or document retrieval. If your TMS is fine except for one thing, replace that thing rather than the system around it.

What is API Plus?

API Plus is what sits between a carrier's raw API and a number you can actually quote on. A carrier API answers the question it was built to answer, in the shape the carrier chose, with whatever their documentation happens to cover. It is a starting point, not an answer — published accessorial lists that do not match what actually prices, rules that exist in the tariff and not in the response, and carriers with no usable API at all. API Plus is the layer that reconciles all of that into one consistent contract, so what comes back is the same shape from every carrier and complete enough to bill against.

One shape for every carrier

Carriers model rates, accessorials and status differently. You get one contract across all of them instead of an integration per carrier and a translation layer you maintain.

The rules the API leaves out

Accessorial triggers, volume and linear-foot rules, carrier quirks that only matter on the loads where they matter. Layered on top so the quote reconciles to the invoice.

Carriers without an API

Plenty of carriers still have no usable API. Credentialed portal access and document parsing bring those into the same feed, so coverage is not limited to whoever shipped a developer portal.

What you can call

Rate

Single or batch, across carrier APIs, your own contracts and internal logic on a base tariff.

Tender

Book the load with the carrier and get the pro number and paperwork back.

Track

Status normalized across carriers, including the ones whose tracking is thin.

Documents

Pull BOLs, delivery receipts and invoices from the carrier automatically.

Audit

Discrepancies against what was quoted, while the load is still moving.

Data

Your own shipment, rate and exception data back out, for your BI or your customers'.

MCP: let an assistant use your freight system

An API is something a developer integrates. MCP — the Model Context Protocol — is how an AI assistant talks to a system directly, with no integration project in between. Same capabilities, exposed so that Claude, ChatGPT or an agent you build yourself can rate a shipment, look up an exception or pull a document because someone asked it to in plain language.

What follows are things you could build on it — not products we sell or run for you.

We expose the capability. What you point at it, and what you automate with it, is yours.

Ask your own freight data anything

Point your assistant at it and ask "what did we pay into Dallas last quarter, and how much of it was accessorials?" It answers from your own shipments, in whatever tool your team already has open. Nothing for us to build first.

Build an email agent that chases

You could have an agent read an incoming reweigh notice, match it to the load, check it against what was quoted and draft the carrier reply with the pro number and documents attached — a person still approves and sends. Your agent, your rules.

Quote without leaving the thread

A customer emails asking for a rate. Your assistant can quote it against your contracts and draft the response in the inbox where the request landed, rather than in a tab somebody has to go and open.

Triage exceptions your way

Audit surfaces the discrepancies; what you do with them is up to you. An agent could group them by cause and put only the ones worth arguing in front of a person, on whatever threshold you decide is worth the effort.

Quick connections

Standing up a useful connection becomes a conversation with an assistant rather than a development ticket. For a small 3PL with no dev team, that is the difference between integrated and not — and it does not wait on our roadmap.

Your agents, not ours

The protocol is open, so none of the above needs us to build it. You are calling the same capabilities our own interface calls, with whatever tooling you already use.

Priced on transactions, not seats

Per-seat and per-license pricing ties your cost to headcount rather than freight, and you find out how much leverage you have at renewal. Transaction pricing means integrating more deeply does not cost you more for the privilege of using it. See the rating engine for how the quoting side works, or integrations for what it already connects to.

Talk through your integration

Building on it

How to evaluate a rating source, and what AI is actually good for here.

Rating & Quoting

Tell us what you want to call

Whether it's the whole platform or one service dropped into a TMS you already run, tell us what you're integrating and we'll tell you what it takes.