Parse AIS vessel position data to track container ship location and estimated port arrival for an ocean freight shipment
domain: logistics-general · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Subscribe to a commercial AIS data provider (e.g., MarineTraffic, VesselFinder) API and authenticate using your API key
Query vessel positions by IMO number or MMSI to retrieve the vessel's current latitude, longitude, speed, heading, and destination as reported in AIS broadcasts
Correlate the vessel name with the bill of lading to confirm you are tracking the correct vessel for your cargo
Use the vessel's current position and average speed to calculate a naive ETA to the destination port; supplement with the provider's own ETA estimate if available
Poll position data at a frequency appropriate to the voyage stage (less frequently on open ocean, more frequently when approaching a port area)
Combine AIS vessel arrival with terminal API data for berth assignment and container gate-out status to build a complete last-mile ETA
Known gotchas
AIS data is self-reported by vessels and can be spoofed, delayed, or absent in areas with poor satellite coverage; treat it as an estimate rather than ground truth
Vessels frequently change their AIS destination field; the reported destination may not reflect the actual next port of call if a transshipment is involved
Correlating AIS vessel data with a specific container requires knowing the voyage and vessel booking; the AIS MMSI alone does not identify individual cargo units
Give your agent this knowledge — and 15,600+ 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?