API integrations and data sync · Live · since July 2026
The covered sweep.
Never quote a taken load: a 15-minute cron reconciles open loads against the TMS and closes them down, never up.
The problem
In the owner's words: never tell a carrier a load is available when it is not. A load gets covered in the TMS, and the lookup and the negotiation bot do not know yet.
How it works
- A 15-minute cloud cron reconciles open loads against the TMS, business hours only.
- The signal is a carrier on the load, not the status. Status looks obvious and is wrong twice: uncovered loads are born committed, and past-quote includes canceled.
- One-way by design: the sweep only closes loads down, every write is guarded on the column still being empty, a human's manual mark is never overwritten, and reopening is human-only. A source column records whether the robot or a person decided.
- The kill switch is an environment variable with off, dry and live settings, so silencing a misbehaving sweep never depends on the database being awake.
// the sweep only ever narrows; a human's decision is never overwritten by a robot's
The result
The lookup and the negotiation bot stopped quoting taken loads within 15 minutes of coverage, with zero extra wiring, because the sweep sets the one flag both already respected.
In practice
Schedule of the unattended systems, Central time.
Syncing the Central clock.
Related systems
- Shadow
The carrier negotiation bot
Haggles with carriers by email. Every dollar comes from a deterministic ladder; the AI only reads.
How it works - Live
Auto-cancel noise suppression
Releases timed-out loads before the shipper's noisy email is ever generated. A one-way door with double guards.
How it works
Your version of this exists.
Different industry, same shape: a repetitive workflow, a fragile spreadsheet, an inbox someone babysits. Tell me what the manual work looks like and I can usually name the first build in one conversation.