Retrieve vessel positions and port calls from the MarineTraffic API
domain: marinetraffic.com (Kpler) · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register for a MarineTraffic API account and purchase/allocate a prepaid credit balance for the specific API service(s) you need.
Obtain your per-service API key from the MarineTraffic API Services dashboard.
Call a positions endpoint (e.g., export vessels by area or by specific vessel) with your key and vessel identifiers (MMSI/IMO/SHIP_ID) or a bounding box.
Call the port calls / events endpoint separately, scoped by vessel or by port, to get arrival/departure/berth timelines.
Parse the returned rows, tracking credit consumption since responses are metered per row/field returned.
Known gotchas
Billing is prepaid-credit based and metered per response row/column, not a flat request count - large queries can consume credits quickly.
MarineTraffic is now part of Kpler post-acquisition; documentation/endpoints are transitioning to Kpler-branded domains - confirm you're on current docs.
Each API "service" (positions, port calls, etc.) is typically a separately purchased product with its own key, not one universal key for all endpoints.
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?