Obtain an ABI filer code from CBP and transmit an Entry Type 01 formal consumption entry through ACE ABI using CATAIR messaging
domain: cbp.gov · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Apply to CBP for a licensed customs broker filer code; confirm your software vendor is on the CBP-approved ABI vendor list at cbp.gov/trade/automated.
Establish a system-to-system EDI connection to ACE ABI using the transmission specifications in the relevant CATAIR chapter for cargo release.
Build the SE (Entry Summary) transaction set following CATAIR field-by-field requirements: importer of record EIN, entry number, HTS codes, entered value, and applicable PGA data elements.
Transmit the entry to CBP in the test environment; validate the 824 Application Advice response codes and correct any rejected segments before moving to production.
In production, transmit the entry and poll for the CBP-generated status messages (e.g., release notification or exam hold) via ABI response transactions.
Archive the filed entry summary, all response messages, and supporting commercial documents for the CBP-mandated five-year retention period.
Known gotchas
ABI is EDI-based, not REST; there is no HTTP endpoint to call. Integration requires a certified ABI software package or a licensed service bureau.
Each HTS number must include the correct statistical suffix and any applicable Chapter 99 tariff overlay; omitting these triggers a CBP reject or penalty.
PGA data (FDA, EPA, USDA, etc.) must be included in the same ABI transmission for covered commodities; separate filing is not allowed for ABI entries.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?