Customs Agent
The Domain Execution Agent behind the Customs & Global Trade Operations add-on — a jurisdiction-aware specialist for broker authorization, Incoterms, and tariff-classification paperwork, plus eleven dedicated reasoning capabilities covering trade compliance, declarations, clearance, freight, and duty across the add-on's screens.
What Is the Customs Agent?
Customs Agent is the specialist behind every AI-calling and jurisdiction-aware screen in the Customs & Global Trade Operations add-on. It combines two distinct kinds of expertise:
- Jurisdiction-aware paperwork — given a country and a document type, it prepares the correct broker-authorization, Incoterms-rule, or tariff-classification form for that jurisdiction (Turkey's GTİP tariff system, the US HTS system, or a generic fallback for any other country), the same way a customs broker would reach for the right country-specific form.
- Eleven dedicated reasoning capabilities, one per screen in the add-on, each reviewing its own kind of trade document and returning a structured judgment — a risk flag, a discrepancy, a recommendation — grounded in the tenant's own trade records.
In one sentence
Customs Agent is where every trade-compliance judgment call in Customs & Global Trade Operations actually happens — it first finds the relevant sanction rules, declarations, or freight records already on file, then reasons over them the way a customs specialist would.
How the Agent Builds Its Context
Every screen in Customs & Global Trade Operations follows the same two-step approach, and Customs Agent always provides the second step:
| Step | What it does |
|---|---|
| Step 1 | Searches the tenant's own live records — sanction rules, declarations, clearance records, freight benchmarks — for the ones relevant to the document being reviewed, entirely on the user's own device. |
| Step 2 | Takes the most relevant matches and reasons over them — risk scoring, overcharge/overpayment detection, discrepancy diagnosis, and more — producing the structured finding the screen displays. |
The candidate pool is always the tenant's own ledger
Customs Agent ranks against the tenant's own live records rather than an external regulation archive — there is no separate government sanctions list or tariff schedule wired in yet. "Search Similar Rules" on the Trade Compliance screen, for instance, ranks the sanction rules already on file for that tenant.
Part 1 — Jurisdiction-Specific Trade Paperwork
Given a country code and a document type, Customs Agent prepares the matching form for that jurisdiction:
| Jurisdiction | Tariff system | Notes |
|---|---|---|
| Turkey | GTİP — 12-digit tariff code | TSE/CE/Tareks permit fields included |
| United States | HTS — 10-digit tariff code | FDA/EPA/FCC permit fields included |
| Any other country | Generic fallback fields | Never fails to return a usable form, even for an unmapped jurisdiction |
Each document type carries its own field set:
Broker Authorization
Customs registration number, Power of Attorney reference and expiry date, digital signature certificate number, and assigned customs offices — powers the Customs Brokers & Agencies screen's authorization modal.
Incoterms Rules
Incoterm code, risk transfer point, buyer freight-cost share, buyer risk share, and (Turkey only) a VAT exemption code — powers the Incoterms & Delivery Rules screen.
Tariff Classification
HS/GTİP or HTS code, product description, duty rate, excise rate (Turkey only), and required permits/certifications — powers the HS Code Catalog screen.
Part 2 — Eleven Trade Reasoning Capabilities
Every reasoning screen in Customs & Global Trade Operations is backed by its own dedicated capability, each grounded in the same kind of trade documents a customs specialist reviews every day:
| Screen it powers | What it computes |
|---|---|
| Trade Compliance & Sanctions | Denied-party match, dual-use license requirement, military-use risk vector, and required documentation for a proposed export/shipment. |
| Export Declarations | Missing invoice details, dual-use export flag, and currency valuation variance note for an outbound filing. |
| Import Declarations | Undervaluation risk warning, reference price gap, and a safety-inspection hold recommendation. |
| Clearance Status | Routing motive, predicted additional delay, and whether a physical inspection is likely. |
| Certificates & Origin Docs | Regional Value Content threshold check, non-originating material risk, and chamber-endorsement verification for a preferential origin document. |
| Freight Rate Benchmark | Carrier overcharge detection, spot-rate arbitrage opportunity, and an estimated price leakage amount for a shipping lane. |
| Global Shipment Tracking | Predicted arrival variance, free-time expiration urgency, and a recommended container gate-out priority. |
| Carrier & Forwarder Hub | SLA contract-breach detection, booking allocation drop detection, and a hazardous-cargo handling accuracy estimate for a logistics provider. |
| Landed Cost Calculator | Duty-spike detection, misallocated terminal-charge flag, and a sanity-check recalculated per-unit landed cost. |
| Customs Duty & Tariff Ledger | Overpayment detection, drawback (refund) eligibility, miscalculated tariff-bracket flag, and an estimated refund amount. |
| Doc Matcher & Linter | Net weight gap, HS code mismatch, and currency discrepancy flags across a shipment's paired documents. |
Why eleven separate capabilities instead of one general one?
A sanctions-screening judgment and a duty-drawback judgment reason about completely different things and produce a different kind of finding. Keeping them separate means a refinement to one screen's judgment can never silently affect another's — the same discipline a specialist applies by keeping distinct checklists for distinct kinds of review.
Where the Customs Agent Fits
Customs Agent has no ledger of its own — every screen's records (sanction rules, declarations, clearance records, freight benchmarks, duty entries) live in the add-on's own tenant-scoped store. Customs Agent's job is strictly the reasoning step: given the context a screen already assembled, produce a structured judgment and hand it back to the person responsible for that record.
A reasoning layer, not a data layer
Customs Agent never reads or writes a tenant's stored records directly — it receives exactly the context the calling screen assembled, reasons over it, and returns a result. Persisting that result back into the screen's own ledger, and any follow-up action a user takes on it, is the calling screen's own responsibility.