Retrieve predictive port-congestion and destination-ETA estimates for vessels approaching a marina's port using MarineTraffic's Predictive Events API.
domain: servicedocs.marinetraffic.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Use existing MarineTraffic (Kpler) API credentials and credit balance
Call the Predictive Events endpoint scoped by port_id or vessel identifier
Parse predicted arrival time, congestion score, and confidence/model metadata fields
Compare predictive ETA against actual Port Calls data (a separate endpoint) once the vessel arrives to gauge model accuracy for your route
Cache/refresh according to the documented update interval to conserve credits
Known gotchas
Predictive/forecast data is modeled, not observed - treat congestion scores and predicted ETAs as planning aids only
This is a distinct, separately priced endpoint from the Port Calls (Real-Time/Past Events) API already used for arrival confirmation; also don't confuse it with the newer, container-specific Predictive Schedules API, a related but separate Kpler product
MarineTraffic's transition into Kpler branding means some newer docs live under kpler.com domains - confirm current servicedocs.marinetraffic.com paths
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?