Trade & customs · Case study
Same brokers. More filings.
An agentic workbench over your certified filing platform. It reads messy trade documents, bills of lading, commercial invoices, packing lists, certificates of origin, extracts every field with its source, proposes HS classifications, and flags conflicts. The broker reviews a sourced draft instead of typing from scratch.
Documents → Draft → Filed
The broker holds the pen.
The agent has no path to the filing authority; accountability stays human by design, and the correction corpus your brokers build stays yours.
A horizontal platform can govern your models. It can’t tell a clean bill of lading from a corrupted EDI feed. We build the production-grade agent workbenches that map to your actual trade and distribution workflows, on data pipelines we’ve already proven in the field.
Case study · Customs document intake
In production
The customs entry that drafts itself.
US customs filing and trade-compliance software provider · details anonymised
14:22, Virginia Beach. An importer emails eleven PDFs: “here’s everything for the Ningbo shipment.”
The problem
A licensed broker’s day begins as data entry. Importers send paperwork however it arrives: a dozen PDFs, phone photos, one bundled scan. Someone keys every value into an entry by hand, reconciling commercial invoice against packing list against bill of lading. It is slow, measured in multi-day email threads, and it spends the broker’s licensed judgment on transcription. When a figure is later questioned, no one can say which document it came from.
What we built
An agentic document-intake pipeline over the client’s existing certified filing platform. Customers upload whatever they have; agents classify each document page by page, extract every field stamped with its source document and page, and cross-check values across documents, proposing which value governs, citing the rule and flagging conflicts. A licensed broker reviews a fully sourced draft and files through the certified path.
Extraction you can trace. Every value is one click from the document and page it was read from.
Gaps are declared, not guessed. The pipeline states plainly what it could not resolve.
Only the broker files with CBP. The authority boundary is structural, not a setting. Accountability stays with the licensed broker.
Business outcomes
Walkthrough
~9 min
Upload to filed, in the walkthrough, against days of email.
In production
Review, not entry
The broker’s first action is judgment; transcription is removed.
Structural
Every field
Traceable to the source document and page it came from.
Structural
100% broker-confirmed
Every filing is submitted only after the broker’s explicit confirmation.
De-risk
Certified path unchanged
The workbench runs on top of your CBP-certified filing platform, which stays exactly as it is.
Why it holds
A filing-type-agnostic spine: the same pattern extends to export and manifest filings next, and is structurally hard to replicate for anyone without the certified platform underneath it.
Stack
Agentic pipeline · Vision models · MCP · Certified ABI/ACE path · Decision Core