File Seafood Import Monitoring Program (SIMP) harvest and chain-of-custody data at U.S. entry via CBP's ACE/ITDS
domain: cbp.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain a NOAA Fisheries International Fisheries Trade Permit (IFTP) as the importer of record before filing any SIMP-covered entry.
Confirm the product falls under one of the 13 SIMP priority species groups using NOAA's compliance guide or the Seafood Import/Export Tool.
Work with a customs broker to submit the required harvest/landing 'message set' data through the Automated Commercial Environment (ACE) via the Automated Broker Interface (ABI), routed through the International Trade Data System (ITDS).
Retain chain-of-custody records from point of harvest through entry into U.S. commerce for the required retention period, even though only summary data is transmitted at entry.
Reference CBP's published NMFS SIMP automated interface requirements implementation guide for the exact ABI record layouts/message set fields the filing software must support.
Known gotchas
SIMP is filed through the same ACE/ABI channel used for general customs entries — it is not a separate standalone public API; a broker or ABI-capable filing software is required, not a direct NOAA endpoint.
Recordkeeping obligations (harvest-to-entry chain of custody) apply even when the transmitted message set itself is only a data summary — auditors can request the full underlying documentation later.
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?