MarineTraffic website screenshot

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.

MarineTraffic publishes 14 APIs on the APIs.io network, including AIS API API, Balances API, Fleets API, and 11 more. Tagged areas include AIS, Maritime, Vessel Tracking, Shipping, and Ports.

The MarineTraffic catalog on APIs.io includes 1 JSON-LD context and 2 Spectral governance rulesets.

MarineTraffic’s developer surface includes developer portal, documentation, API reference, support, sandbox, tooling, and 16 more developer resources.

🌐 Visit website 📡 Source on GitHub
45.7/100 developing ▬ flat Agent 35/100 agent ready Full breakdown ↓
scored 2026-07-28 · rubric v0.6
AccessEnterprise
14 APIs 20 Features 7 Use Cases
AISMaritimeVessel TrackingShippingPortsVoyage ForecastingGeospatialKpler

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-07-28 · rubric v0.6
Composite quality — 45.7/100 · developing
Contract Quality 17.6 / 25
Developer Ergonomics 7.0 / 20
Commercial Clarity 5.8 / 20
Operational Transparency 0.7 / 13
Governance 8.3 / 12
Discoverability 6.5 / 10
Agent readiness — 35/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 10 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 8 / 8
Request/Response Examples 7 / 7
Rate-Limit Signaling 7 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/marine-traffic: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

APIs 14

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 for all 14

Open Collections 9

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

MarineTraffic Events API

OPEN COLLECTION

MarineTraffic Ports Information API

OPEN COLLECTION

MarineTraffic Power User API

OPEN COLLECTION

MarineTraffic Reverse Geocoding API

OPEN COLLECTION

MarineTraffic Routing Information API

OPEN COLLECTION

MarineTraffic Vessel Positions API

OPEN COLLECTION

MarineTraffic Vessels Data API

OPEN COLLECTION

MarineTraffic Voyage Information API

OPEN COLLECTION

MarineTraffic AIS Data API

OPEN COLLECTION

Scroll for all 9

Pricing Plans 1

Published pricing tiers and plan structures.

Marine Traffic Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Marine Traffic Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Marine Traffic Finops

FINOPS

Features 20

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 for all 20

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Marine Traffic Context

0 classes · 7 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

MarineTraffic API Rules

5 rules · 4 warnings 1 info

SPECTRAL

MarineTraffic API Rules

7 rules · 2 errors 4 warnings 1 info

SPECTRAL

JSON Schema 5

Standalone JSON Schema definitions for this provider's data models.

MarineTraffic Port Call

24 properties

JSON SCHEMA

MarineTraffic Port

12 properties

JSON SCHEMA

MarineTraffic Vessel Master Data

23 properties

JSON SCHEMA

MarineTraffic Vessel Position

28 properties

JSON SCHEMA

MarineTraffic Voyage Forecast

13 properties

JSON SCHEMA

Examples 3

Example request and response payloads for these APIs.

Marine Traffic Port Call Example

20 fields

EXAMPLE

Marine Traffic Vessel Position Example

28 fields

EXAMPLE

Marine Traffic Voyage Forecast Example

13 fields

EXAMPLE

Security Posture 1

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Marine Traffic Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Marine Traffic Agentic Access

78 operations · 2 acting

78 operations · 2 acting

AGENTIC

Use Cases 7

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 for all 7

Integrations 5

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 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

Get Started 3

Portal, sign-up, and the first successful call

Portal
Portal
 Portal
Portal
 Sandbox
Sandbox

Documentation 4

Reference material describing how the API behaves

Documentation
Documentation
 APIReference
APIReference
 Documentation
Documentation
 OpenAPI
OpenAPI

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

AgenticAccess
AgenticAccess

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

ErrorCodes
ErrorCodes
 SpectralRules
SpectralRules
 Vocabulary
Vocabulary
 JSONLD
JSONLD

Build 2

SDKs, sample code, and the tooling you integrate with

GitHubOrganization
GitHubOrganization
 Tools
Tools

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity
DomainSecurity

Operate 3

Status, limits, changes, and where to get help

Support
Support
 Support
Support
 RateLimits
RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans
Plans
 FinOps
FinOps

Company 2

The organization behind the API

LinkedIn
LinkedIn
 Twitter
Twitter

Source (apis.yml)

apis.yml Raw ↑ 
aid: marine-traffic
url: https://raw.githubusercontent.com/api-evangelist/marine-traffic/refs/heads/main/apis.yml
apis:
- aid: marine-traffic:marine-traffic-ais-api-api
  name: MarineTraffic AIS API API
  description: The AIS API API from MarineTraffic — 3 operation(s) for ais api.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - AIS API
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-ais-api-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-balances-api
  name: MarineTraffic Balances API
  description: The Balances API from MarineTraffic — 1 operation(s) for balances.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Balances
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-balances-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-fleets-api
  name: MarineTraffic Fleets API
  description: The Fleets API from MarineTraffic — 4 operation(s) for fleets.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Fleets
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-fleets-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-passage-plans-api
  name: MarineTraffic Passage Plans API
  description: The Passage Plans API from MarineTraffic — 1 operation(s) for passage plans.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Passage Plans
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-passage-plans-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-port-events-api
  name: MarineTraffic Port Events API
  description: The Port Events API from MarineTraffic — 2 operation(s) for port events.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Port Events
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-port-events-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-ports-information-api
  name: MarineTraffic Ports Information API
  description: The Ports Information API from MarineTraffic — 4 operation(s) for ports information.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Ports Information
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-ports-information-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-reverse-geocoding-api
  name: MarineTraffic Reverse Geocoding API
  description: The Reverse Geocoding API from MarineTraffic — 1 operation(s) for reverse geocoding.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Reverse Geocoding
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-reverse-geocoding-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-routing-information-api
  name: MarineTraffic Routing Information API
  description: The Routing Information API from MarineTraffic — 2 operation(s) for routing information.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Routing Information
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-routing-information-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-search-vessel-api
  name: MarineTraffic Search Vessel API
  description: The Search Vessel API from MarineTraffic — 2 operation(s) for search vessel.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Search Vessel
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-search-vessel-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-single-vessel-events-api
  name: MarineTraffic Single Vessel Events API
  description: The Single Vessel Events API from MarineTraffic — 3 operation(s) for single vessel events.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Single Vessel Events
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-single-vessel-events-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-vessel-historical-track-api
  name: MarineTraffic Vessel Historical Track API
  description: The Vessel Historical Track API from MarineTraffic — 2 operation(s) for vessel historical track.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Vessel Historical Track
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-vessel-historical-track-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-vessel-information-api
  name: MarineTraffic Vessel Information API
  description: The Vessel Information API from MarineTraffic — 2 operation(s) for vessel information.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Vessel Information
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-vessel-information-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-vessel-positions-legacy-api-api
  name: MarineTraffic Vessel Positions (Legacy API) API
  description: The Vessel Positions (Legacy API) API from MarineTraffic — 7 operation(s) for vessel positions (legacy api).
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Vessel Positions (Legacy API)
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-vessel-positions-legacy-api-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
- aid: marine-traffic:marine-traffic-voyage-information-api
  name: MarineTraffic Voyage Information API
  description: The Voyage Information API from MarineTraffic — 5 operation(s) for voyage information.
  humanURL: https://servicedocs.marinetraffic.com/
  tags:
  - Voyage Information
  properties:
  - type: OpenAPI
    url: openapi/marine-traffic-voyage-information-api-openapi.yml
  - type: Documentation
    url: https://servicedocs.marinetraffic.com/
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-position-schema.json
  - type: JSONLD
    url: json-ld/marine-traffic-context.jsonld
  - type: Examples
    url: examples/marine-traffic-vessel-position-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-call-schema.json
  - type: Examples
    url: examples/marine-traffic-port-call-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-vessel-master-schema.json
  - type: JSONSchema
    url: json-schema/marine-traffic-voyage-forecast-schema.json
  - type: Examples
    url: examples/marine-traffic-voyage-forecast-example.json
  - type: JSONSchema
    url: json-schema/marine-traffic-port-schema.json
name: MarineTraffic
tags:
- AIS
- Maritime
- Vessel Tracking
- Shipping
- Ports
- Voyage Forecasting
- Geospatial
- Kpler
kind: contract
accessModel:
  pricing: enterprise
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: medium
  source:
  - plans
  generated: '2026-07-22'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/marine-traffic.png
access: 3rd-Party
common:
- type: AgenticAccess
  url: agentic-access/marine-traffic-agentic-access.yml
- type: DomainSecurity
  url: security/marine-traffic-domain-security.yml
- url: https://www.marinetraffic.com/
  name: MarineTraffic
  type: Portal
- url: https://servicedocs.marinetraffic.com/
  name: AIS Data API Reference
  type: Documentation
- url: https://servicedocs.marinetraffic.com/
  name: API Reference
  type: APIReference
- url: https://www.kpler.com/product/maritime/data-services
  name: Kpler / MarineTraffic Maritime Data Services
  type: Portal
- url: https://support.marinetraffic.com/en/articles/9552659-api-services
  name: API Services — Common Problems and Solutions
  type: Support
- url: https://support.marinetraffic.com/en/articles/9552800-api-most-common-response-error-codes
  name: API Most Common Response Error Codes
  type: ErrorCodes
- url: https://support.marinetraffic.com/en/articles/9552860-what-kind-of-information-is-ais-transmitted
  name: What Kind of Information is AIS Transmitted
  type: Documentation
- url: https://support.marinetraffic.com/
  name: MarineTraffic Support Center
  type: Support
- url: https://www.marinetraffic.com/en/ais/home
  name: MarineTraffic Live Map
  type: Sandbox
- url: https://github.com/marinetraffic
  name: MarineTraffic on GitHub
  type: GitHubOrganization
- url: https://github.com/marinetraffic/mt-ais-toolbox
  name: mt-ais-toolbox — AIS Density Map Toolbox
  type: Tools
- url: https://www.linkedin.com/company/marinetraffic
  name: MarineTraffic on LinkedIn
  type: LinkedIn
- url: https://twitter.com/MarineTraffic
  name: MarineTraffic on Twitter / X
  type: Twitter
- url: openapi/marine-traffic-openapi.yml
  type: OpenAPI
  name: Combined MarineTraffic AIS Data API (all surfaces)
- url: rules/marine-traffic-rules.yml
  type: SpectralRules
- url: vocabulary/marine-traffic-vocabulary.yml
  type: Vocabulary
- url: json-ld/marine-traffic-context.jsonld
  type: JSONLD
- url: plans/marine-traffic-plans-pricing.yml
  type: Plans
- url: rate-limits/marine-traffic-rate-limits.yml
  type: RateLimits
- url: finops/marine-traffic-finops.yml
  type: FinOps
- type: Features
  data:
  - name: AIS vessel positions (live + delayed)
    description: 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 hour; real-time access via enterprise contract.
  - name: Vessel historical track
    description: Replay a vessel's AIS track over a defined date / day window.
  - name: Port calls and berth calls
    description: Provider-detected arrival, departure, and berth-touch events per vessel and per port, with voyage duration
      and time-in-port.
  - name: Vessel master data
    description: Static AIS plus MarineTraffic-enriched fields — owner, manager, builder, class, build year, dimensions, deadweight,
      gross tonnage.
  - name: Vessel photographs
    description: Ship-photo retrieval via VD01.
  - name: Vessel search
    description: Search the ship database by identifier (IMO / MMSI / SHIP_ID / call sign) or by name.
  - name: Voyage forecasts
    description: Predictive destination, ETA, and route distance for a single vessel or a whole fleet (VI01).
  - name: Predictive destination areas
    description: Probability-ranked candidate destination ports for a vessel or fleet (VI04).
  - name: ETA to port
    description: Predictive ETA to a specific destination port (VI07).
  - name: Expected and predictive port arrivals
    description: Per-port arrival forecasts (VI02 / VI05) filtered by market, ship class, draught, and time window.
  - name: Port congestion analytics
    description: Anchorage time, in-port time, vessel and call counts per port / market / ship-class / ISO week (VI06).
  - name: Maritime routing
    description: Sea-lane-aware route + distance computation between origin and destination (VI03).
  - name: Reverse geocoding
    description: Coordinate-to-maritime-location resolution (port, anchorage, berth, terminal, custom area) (GI01).
  - name: Fleet management
    description: CRUD on power-user fleets — set, get, list, clear (PU01–PU05).
  - name: Account credit balance
    description: Live balance inspection via /exportcredits (free).
  - name: Passage plan import
    description: POST /import-passage-plan to ingest voyage plans for power-user fleets.
  - name: Multiple response protocols
    description: Per-call response format — json (default), jsono, xml, csv — via the protocol query parameter.
  - name: 13,000+ terrestrial AIS receivers + satellite AIS
    description: Hybrid global coverage operated by Kpler / MarineTraffic.
  - name: Live NMEA streams (enterprise)
    description: Direct NMEA AIS streams available as an enterprise data product alongside the REST API.
  - name: Cloud database / bulk delivery (enterprise)
    description: Hosted cloud-database access and bulk CSV deliveries for high-volume customers.
  sources:
  - https://servicedocs.marinetraffic.com/
  - https://www.kpler.com/product/maritime/data-services
  updated: '2026-05-25'
- type: UseCases
  data:
  - name: Commodity trading and freight intelligence
    description: Power voyage analytics, tonnage tracking, and supply forecasting for commodity desks.
  - name: Port operations and logistics
    description: Anticipate berth demand, optimize pilotage and tug allocation, and reduce dwell.
  - name: Vessel tracking dashboards
    description: Build fleet dashboards and customer-facing tracking pages using PS04 + VI07.
  - name: Compliance and sanctions monitoring
    description: Detect dark fleet behavior, AIS gaps, port-call patterns, and sanctioned vessel touches.
  - name: Marine insurance underwriting
    description: Underwrite hull / P&I and route insurance with verified call histories and port-congestion data.
  - name: Government and coast guard situational awareness
    description: Feed maritime domain awareness systems with AIS, port-call, and routing context.
  - name: Carbon and ESG reporting
    description: Compute voyage-level CO2 estimates by combining VI03 routing + VD02 master data + AIS speed.
- type: Integrations
  data:
  - name: Kpler
    description: MarineTraffic is part of the Kpler maritime intelligence platform; AIS APIs sit alongside Kpler trade flow
      data.
  - name: Postman / API clients
    description: Standard REST + JSON; works directly in Postman, Insomnia, or any HTTP client.
  - name: GIS / mapping
    description: Output is lat/lon-tagged — integrates with QGIS, Mapbox, Leaflet, and Esri.
  - name: NMEA-compatible bridge systems
    description: Enterprise NMEA streams integrate with ECDIS, fleet-management software, and bridge electronics.
  - name: AIS density-map toolbox
    description: MarineTraffic publishes mt-ais-toolbox on GitHub for density-map generation from AIS data.
- type: Solutions
  data:
  - name: Self-serve REST API
    description: Public REST APIs metered against a prepaid credit balance — what this catalog covers.
  - name: NMEA live AIS streams
    description: Raw NMEA AIS for bridge-side and processing-pipeline customers (enterprise).
  - name: Cloud database access
    description: Hosted MarineTraffic database for SQL / analytics workloads (enterprise).
  - name: Custom data extracts
    description: Bespoke CSV / JSON delivery against custom queries (enterprise).
created: '2026-05-25T00:00:00.000Z'
modified: '2026-05-25'
position: Consuming
description: 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.
maintainers:
- FN: Kin Lane
  email: info@apievangelist.com
  X: apievangelist
  url: https://apievangelist.com
specificationVersion: '0.16'