FleetMon
FleetMon was a Rostock, Germany based vessel tracking and maritime data provider (founded 2007) that operated one of the world's largest terrestrial AIS receiver networks and a documented REST API (apiv2.fleetmon.com) for vessel search, live and historical AIS positions, port calls, expected arrivals, ETA and voyage planning. Kpler acquired FleetMon alongside MarineTraffic in 2023, the FleetMon platform and API were phased out from January 2024 and migrated into MarineTraffic, and in September 2025 the combined AIS assets were unified under the Kpler AIS brand. As of 2026 the fleetmon.com domain, developer portal, and API no longer resolve - this entry preserves the final archived API surface and points to the Kpler / MarineTraffic successor services.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles FleetMon the way a machine reads it — 78 machine-readable artifacts across 1 API, 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 — FleetMon scores 21.5/100 (emerging), with a separate agent-readiness read of 22/100 (agent aware). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from FleetMon's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fleetmon/"
title="FleetMon on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fleetmon.svg"
alt="FleetMon Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/fleetmon/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/fleetmon/"
title="FleetMon on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/fleetmon/card.svg"
alt="FleetMon Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile FleetMon
Each block below is one kind of artifact we hold for FleetMon. 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 37
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.
FleetMon Basic Vessel Data API
Delivers basic static data for a vessel.
FleetMon Current API
Returns current info for lat/lon (and timestamp).
FleetMon Distance To Port API
Returns the high level summary of a route to port, only including distance, costs, and the count of edges from the routing graph.
FleetMon Estimated Laytime - Specific Vessel API
This API returns an estimated laytime for a vessel in all terminals of a port.
FleetMon Expected Port Arrivals API
Lists vessels heading for a specific port, matched by AIS destination.
FleetMon Fleet Tracker API
Tracking of current positions for a modifiable list of vessels.
FleetMon Historical AIS Static Messages API
Delivers AIS messages of type 5, 19 & 24 for a specified MMSI number.
FleetMon Historical Track API API
Returns historical AIS position reports with fixed period and rate, by MMSI.
FleetMon Login Token API
Generate new Login Tokens with Token Keys
FleetMon Logistics API
Delivers information about the vessels current state and the next port it is heading for.
FleetMon My Fleet Positions API
Delivers your MyFleet or a single vessel of it.
FleetMon Next Port / ETA Calculation API
Delivers information about the next port, provided by the vessel itself via AIS destination.
FleetMon Non AIS Vessel Particulars API
Delivers owner, manager, DWT, GT and a photo-URL for a vessel, if it's available.
FleetMon Port Calls per Port API
Delivers portcalls for a port.
FleetMon Port Calls per Vessel API
Delivers portcalls for a vessel.
FleetMon Port Search API
Allows lookup of ports by UN/LOCODE, name and/or country.
FleetMon Regional AIS API
delivers AIS informations for a predefined bounding box
FleetMon RoRo Ferry Terminal Demo API
This API deliver the enter and left event of the RoRo-Ferry-Terminal Rostock. It is no API key necessary. The look back is 48h. It will be provides information about the Termina...
FleetMon Vessel Change Events API
Delivers change events for vessels.
FleetMon Vessel Dynamic AIS API
Live Dynamic AIS data from requested vessel
FleetMon Vessel ETA & Destination Change Events API
Delivers ETA & Destination Change for vessels.
FleetMon Vessel Identity API
Returns the identifying attributes of the provided vessel.
FleetMon Vessel Photo API
Delivers the URL to the main photo for a vessel. Look-up can be done by Vessel ID or IMO-number.
FleetMon Vessel Positions Only API
Returns the latest received position.
FleetMon Vessel Positions with Extended Vessel Data API
Delivers position and extended detailed information for a single vessel.
FleetMon Vessel Route From Last Port API
Returns the actual route from last port to latest position.
FleetMon Vessel Route To Next Port API
Returns the route to the next port of a vessel (using ObjectID).
FleetMon Vessel Schedule API
This endpoint provides schedules for vessels, e.g. container schedules.
FleetMon Vessel Search API
Allows searching over the FleetMon vessel database by name, IMO-number, MMSI-number and/or callsign.
FleetMon Vessels in Port API
Lists vessels detected in port for the specified LOCODE.
FleetMon Vessels Near Position API
Vessels near requested position
FleetMon Vessels Nearby API
Vessels nearby requested vessel
FleetMon Voyage Planning API
Delivers ETA & distance estimations for a route with multiple ports specified by LOCODE.
FleetMon Water API
Returns wave info for lat/lon (and timestamp).
FleetMon Weather API
Returns weather info for lat/lon (and timestamp).
FleetMon Zone Call API
Zone Call API
FleetMon Zone Information API
Delivers an overview of your geo-zones.
Scroll within the panel for all 37 ·
Open Collections 38
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).
API Collection
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Current API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Fleet Tracker API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Login Token API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Logistics API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Port Search API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Regional AIS API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Vessel Identity API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Vessel Photo API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Vessel Positions with Extended Vessel Data API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Vessel Schedule API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Vessel Search API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Vessels in Port API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Vessels Nearby API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Voyage Planning API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Water API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Weather API
OPEN COLLECTIONFleetMon API Reference Basic Vessel Data Zone Call API
OPEN COLLECTIONScroll within the panel for all 38 ·
Security Posture 2
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.
Resources
Every other property we hold for FleetMon — 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 1
Portal, sign-up, and the first successful call
Documentation 3
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 2
Authentication, authorization, and security posture
Company 3
The organization behind the API
Other 4
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/fleetmon · machine-readable index on apis.io
This is an independent, third-party profile of FleetMon, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.