You're not booking an MC number. You're trusting a business.
HaulLynx assembles the whole carrier — identity, authority, insurance, every lane, every settlement, every interaction — into one living, connected model of the relationship. Sourced, always current, and yours to see before you book.
Apply for founding access→A relationship isn't a profile. It's a living model.
Most tools store a carrier as a row — a name, an MC number, a phone. HaulLynx builds them as a connected model: the carrier at the center, with every load, lane, document, settlement, exception, and interaction linked to them, and the trust and behavior that accumulate across all of it. Change one fact and the whole picture updates. This is the thing underneath everything else HaulLynx does.
One carrier. Every object, linked. Always current.
Every judgment traces to a real fact in the record.
Because the relationship is a connected model and not a score, Lynx can always show its work. Open any flag and see its source — FMCSA for authority, the document vault for insurance, your own booking history for behavior, settlement records for disputes. Walk the relationship load by load. Nothing is asserted that the model doesn't contain, sourced.
The relationship updates itself.
A profile goes stale the moment you save it. A living model doesn't. Every load, exception, document, and settlement enters the record the moment it happens — and HaulLynx re-checks the facts that change on their own: FMCSA authority daily, insurance certificates before they lapse. So the picture you decide on is the picture as it is right now, and the relationship deepens with every closed loop.
Know who you're working with — and who they've worked with.
Trust circles carry the relationship, not just a face: who's verified, who you've covered freight with before, who's an unfamiliar profile. Pattern-level intelligence across the network surfaces what a single profile can't — while your own dealings stay yours alone.
Investigate your whole network in plain language.
Ask, and Lynx answers from your real records — every result traces back to what it found in the model. It never invents a pattern it didn't compute, and you only ever see your own network, never another broker's.
The record that tells you who to trust also tells you what's off.
The same connected model that shows you who to trust surfaces the anomalies — a double-brokering signal, an authority that lapsed since you last booked, an insurance certificate that expired, a carrier that shares an identifier with a flagged one. HaulLynx watches continuously and surfaces it for your review. It relays the facts and detects the patterns; the call, and the liability, stay yours.
When Montgomery v. Caribe Transport raised the bar on broker liability, continuous verification stopped being optional — so we built it into the model.
An identity or behavior anomaly, surfaced for your review before it costs you.
FMCSA re-checked daily — you know before you book them again. (FMCSA-attributed.)
Document vault flags a lapse before it becomes your exposure.
A shared phone or address to a flagged profile, detected across the network.
See who you're really working with.
Apply for founding access→You're not booking an MC number. You're trusting a business.
HaulLynx assembles the whole carrier — identity, authority, insurance, every lane, every settlement, every interaction — into one living, connected model. Sourced, always current, yours to see before you book.
Apply for founding access→A relationship isn't a profile. It's a living model.
HaulLynx builds the carrier as a connected model: at the center, with every load, lane, document, settlement, exception, and interaction linked to them. Change one fact and the whole picture updates.
One carrier. Every object, linked. Always current.
Every judgment traces to a real fact in the record.
Because it's a model and not a score, Lynx shows its work — open any flag, see its source, walk the relationship load by load.
The relationship updates itself.
Every load, exception, document, and settlement enters the record as it happens — and HaulLynx re-checks FMCSA authority daily and insurance before it lapses. The picture you decide on is the picture right now.
Know who you're working with — and who they've worked with.
Trust circles carry the relationship: who's verified, who you've covered with, who's unfamiliar. Pattern-level intelligence surfaces what a single profile can't.
Investigate your whole network in plain language.
Lynx answers from your real records — it never invents a pattern it didn't compute, and you only see your own network.
The record that tells you who to trust also tells you what's off.
The same connected model surfaces the anomalies — double-brokering, lapsed authority, expired insurance, a shared identifier with a flagged carrier. HaulLynx detects and relays; the call, and the liability, stay yours.
When Montgomery v. Caribe Transport raised the bar on broker liability, continuous verification stopped being optional — so we built it into the model.
An identity or behavior anomaly, surfaced for your review.
FMCSA re-checked daily — you know before booking again.
Document vault flags a lapse before it becomes exposure.
A shared phone or address, detected across the network.