MarineTraffic
MarineTraffic is the leading maritime intelligence and AIS ship-tracking platform — now part of Kpler. The MarineTraffic AIS Data API exposes the same live + historical vessel positions, port calls, berth calls, vessel master data, voyage forecasts, predictive arrivals, port-congestion analytics, sea-lane routing, reverse geocoding, and fleet management endpoints that power the public marinetraffic.com map and the Kpler maritime data services. Data is sourced from 13,000+ terrestrial AIS receivers plus satellite AIS, served as REST/JSON (with CSV / XML / JSONO alternatives), authenticated via a per-key prepaid credit balance, and metered in credits per response row with per-service refresh-interval caching.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles MarineTraffic the way a machine reads it — 75 machine-readable artifacts across 14 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — MarineTraffic scores 49.8/100 (developing), with a separate agent-readiness read of 46/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile MarineTraffic
Each block below is one kind of artifact we hold for MarineTraffic. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 14
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
MarineTraffic AIS API API
The AIS API API from MarineTraffic — 3 operation(s) for ais api.
MarineTraffic Balances API
The Balances API from MarineTraffic — 1 operation(s) for balances.
MarineTraffic Fleets API
The Fleets API from MarineTraffic — 4 operation(s) for fleets.
MarineTraffic Passage Plans API
The Passage Plans API from MarineTraffic — 1 operation(s) for passage plans.
MarineTraffic Port Events API
The Port Events API from MarineTraffic — 2 operation(s) for port events.
MarineTraffic Ports Information API
The Ports Information API from MarineTraffic — 4 operation(s) for ports information.
MarineTraffic Reverse Geocoding API
The Reverse Geocoding API from MarineTraffic — 1 operation(s) for reverse geocoding.
MarineTraffic Routing Information API
The Routing Information API from MarineTraffic — 2 operation(s) for routing information.
MarineTraffic Search Vessel API
The Search Vessel API from MarineTraffic — 2 operation(s) for search vessel.
MarineTraffic Single Vessel Events API
The Single Vessel Events API from MarineTraffic — 3 operation(s) for single vessel events.
MarineTraffic Vessel Historical Track API
The Vessel Historical Track API from MarineTraffic — 2 operation(s) for vessel historical track.
MarineTraffic Vessel Information API
The Vessel Information API from MarineTraffic — 2 operation(s) for vessel information.
MarineTraffic Vessel Positions (Legacy API) API
The Vessel Positions (Legacy API) API from MarineTraffic — 7 operation(s) for vessel positions (legacy api).
MarineTraffic Voyage Information API
The Voyage Information API from MarineTraffic — 5 operation(s) for voyage information.
Scroll within the panel for all 14 ·
Open Collections 9
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
MarineTraffic Events API
OPEN COLLECTIONMarineTraffic Ports Information API
OPEN COLLECTIONMarineTraffic Power User API
OPEN COLLECTIONMarineTraffic Reverse Geocoding API
OPEN COLLECTIONMarineTraffic Routing Information API
OPEN COLLECTIONMarineTraffic Vessel Positions API
OPEN COLLECTIONMarineTraffic Vessels Data API
OPEN COLLECTIONMarineTraffic Voyage Information API
OPEN COLLECTIONMarineTraffic AIS Data API
OPEN COLLECTIONScroll within the panel for all 9 ·
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Marine Traffic Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Marine Traffic Finops
FINOPSFeatures 20
The notable capabilities this provider advertises, captured as structured features so they can be searched and compared instead of read one landing page at a time.
Notable capabilities this provider offers.
AIS vessel positions (live + delayed)
Vessel positions sourced from 13,000+ terrestrial AIS receivers and satellite AIS, accessible by single vessel, fleet, area of interest, port, or bounding box. Default delay 1 h...
Vessel historical track
Replay a vessel's AIS track over a defined date / day window.
Port calls and berth calls
Provider-detected arrival, departure, and berth-touch events per vessel and per port, with voyage duration and time-in-port.
Vessel master data
Static AIS plus MarineTraffic-enriched fields — owner, manager, builder, class, build year, dimensions, deadweight, gross tonnage.
Vessel photographs
Ship-photo retrieval via VD01.
Vessel search
Search the ship database by identifier (IMO / MMSI / SHIP_ID / call sign) or by name.
Voyage forecasts
Predictive destination, ETA, and route distance for a single vessel or a whole fleet (VI01).
Predictive destination areas
Probability-ranked candidate destination ports for a vessel or fleet (VI04).
ETA to port
Predictive ETA to a specific destination port (VI07).
Expected and predictive port arrivals
Per-port arrival forecasts (VI02 / VI05) filtered by market, ship class, draught, and time window.
Port congestion analytics
Anchorage time, in-port time, vessel and call counts per port / market / ship-class / ISO week (VI06).
Maritime routing
Sea-lane-aware route + distance computation between origin and destination (VI03).
Reverse geocoding
Coordinate-to-maritime-location resolution (port, anchorage, berth, terminal, custom area) (GI01).
Fleet management
CRUD on power-user fleets — set, get, list, clear (PU01–PU05).
Account credit balance
Live balance inspection via /exportcredits (free).
Passage plan import
POST /import-passage-plan to ingest voyage plans for power-user fleets.
Multiple response protocols
Per-call response format — json (default), jsono, xml, csv — via the protocol query parameter.
13,000+ terrestrial AIS receivers + satellite AIS
Hybrid global coverage operated by Kpler / MarineTraffic.
Live NMEA streams (enterprise)
Direct NMEA AIS streams available as an enterprise data product alongside the REST API.
Cloud database / bulk delivery (enterprise)
Hosted cloud-database access and bulk CSV deliveries for high-volume customers.
Scroll within the panel for all 20 ·
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Marine Traffic Context
JSON-LDSpectral Rules 2
Governance rulesets we run against this provider's specs — the automated checks behind parts of the score. Profiling them makes the quality bar explicit and re-runnable, not a matter of opinion.
MarineTraffic API Rules
SPECTRALMarineTraffic API Rules
SPECTRALJSON Schema 5
Standalone JSON Schema definitions describe the data models behind the API. We profile them so the shapes are validatable on their own — useful long after a single request is forgotten.
Standalone JSON Schema definitions for this provider's data models.
MarineTraffic Port Call
JSON SCHEMAMarineTraffic Port
JSON SCHEMAMarineTraffic Vessel Master Data
JSON SCHEMAMarineTraffic Vessel Position
JSON SCHEMAMarineTraffic Voyage Forecast
JSON SCHEMAExamples 3
Real request and response payloads are what turn a spec from abstract into obvious — and they're one of the twelve things an agent needs to call an API correctly on the first try.
Example request and response payloads for these APIs.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Use Cases 7
What developers actually build with this provider — captured so the catalogue answers 'what is this for', not just 'what does this expose'.
What developers build with this provider.
Commodity trading and freight intelligence
Power voyage analytics, tonnage tracking, and supply forecasting for commodity desks.
Port operations and logistics
Anticipate berth demand, optimize pilotage and tug allocation, and reduce dwell.
Vessel tracking dashboards
Build fleet dashboards and customer-facing tracking pages using PS04 + VI07.
Compliance and sanctions monitoring
Detect dark fleet behavior, AIS gaps, port-call patterns, and sanctioned vessel touches.
Marine insurance underwriting
Underwrite hull / P&I and route insurance with verified call histories and port-congestion data.
Government and coast guard situational awareness
Feed maritime domain awareness systems with AIS, port-call, and routing context.
Carbon and ESG reporting
Compute voyage-level CO2 estimates by combining VI03 routing + VD02 master data + AIS speed.
Scroll within the panel for all 7 ·
Integrations 5
Pre-built integrations with other platforms tell you where this provider already fits in a stack.
Pre-built integrations with other platforms and tools.
Kpler
MarineTraffic is part of the Kpler maritime intelligence platform; AIS APIs sit alongside Kpler trade flow data.
Postman / API clients
Standard REST + JSON; works directly in Postman, Insomnia, or any HTTP client.
GIS / mapping
Output is lat/lon-tagged — integrates with QGIS, Mapbox, Leaflet, and Esri.
NMEA-compatible bridge systems
Enterprise NMEA streams integrate with ECDIS, fleet-management software, and bridge electronics.
AIS density-map toolbox
MarineTraffic publishes mt-ais-toolbox on GitHub for density-map generation from AIS data.
Solutions 4
Packaged solutions the provider offers on top of the raw API surface.
Packaged solutions this provider offers.
Self-serve REST API
Public REST APIs metered against a prepaid credit balance — what this catalog covers.
NMEA live AIS streams
Raw NMEA AIS for bridge-side and processing-pipeline customers (enterprise).
Cloud database access
Hosted MarineTraffic database for SQL / analytics workloads (enterprise).
Custom data extracts
Bespoke CSV / JSON delivery against custom queries (enterprise).
Resources
Every other property we hold for MarineTraffic — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 3
Portal, sign-up, and the first successful call
Documentation 4
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 1
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/marine-traffic · machine-readable index on apis.io