Browser automation · Live · since August 2026
The carrier purge.
Given a list of DOT numbers, delete those carriers from the TMS the way the UI does, and prove each one is gone.
Livesession replayTMSwritten procedure
The problem
Thousands of blocked and disabled carriers cluttered the TMS carrier list. Deleting one by hand meant search, open, trash can, confirm. The public API turned out to have no delete at all.
How it works
- First the full API surface was enumerated to prove there was no delete, so the browser path was a decision, not a guess.
- The UI's own delete request was captured once and replayed with the session's credentials, one carrier per request, keyed by DOT because older MC numbers lose their leading zero in downloads.
- Every deletion is verified by a fresh read: the carrier's internal ID must come back empty before the row is marked done. The run writes a ledger so a re-run skips what is already gone.
// nothing is marked deleted until a fresh read confirms the carrier is gone
The result
First run: 2,464 carriers deleted and verified from one list. The procedure is written so the next list is a single command.
Related systems
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.