Picture this. You've been handed a project: build voyage and fleet tooling. You need vessel positions, ocean weather, maybe booking events from a big container line. Naturally you open the APIs.io Maritime industry page, and the first number looks reassuring: 73 providers and 447 APIs. That's plenty to work with, you think.
Then you sort by score, and the picture changes. The highest Kin Score in the whole vertical belongs to Tomorrow.io, a Boston weather intelligence platform, at 56.3. It's the only provider in the strong band. You expected a shipping company up there. Instead you find weather, satellite connectivity and AIS tracking ranking above the ocean carriers that move most of the world's containers.
The post explains why. Membership in the industry is computed from tags, not a hand-picked list, so the vertical reflects who touches the sea, not who owns ships. That's how you end up with a weather company on top.
So you look at the vertical by function. Ocean weather and sensors: Tomorrow.io at 56.3, Sofar Ocean at 46.7, Xweather at 41.7. Fleet and ship management: SERTICA at 45.0, Nortech at 45.5, SEDNA at 40.1. Classification: DNV at 45.4. Vessel tracking: VesselFinder at 44.8, MarineTraffic at 40.5, AISStream at 28.9.
Now the carriers, which is where you were hoping to find booking and shipment events. Maersk sits at 43.0. After that the numbers fall away: CMA CGM at 14.3, Hapag-Lloyd at 5.7, MSC at 5.4, COSCO Shipping at 3.3, Matson at 0.6. Maersk has 11 APIs, 8 of them published, more than any other carrier here. MSC, ZIM, Ocean Network Express, COSCO and Matson have no APIs in the catalog at all. The post is careful about what that means: what's missing is a public, machine-readable contract the catalog can find. It isn't a claim about what those companies run internally.
You might still be tempted to trust the big total. Don't. Forty of the 73 providers have an API count of zero. The band split is 1 strong, 11 developing, 8 thin, 15 emerging and 38 minimal, so more than half of maritime is a company record with no surface behind it yet. That includes the Federal Maritime Commission, at 3.3.
And the 447 is skewed too. SERTICA, RINA's fleet and ship management system, accounts for 254 of those APIs, about 57 percent, and it says only 1 of them is published. If you count maritime APIs, you're mostly counting SERTICA's per-module contracts. The total is not a measure of depth.
Here's the turn, and it's the part worth sitting with. The catalog is reporting on itself as much as on the industry. The carriers aren't shown as failing; the gap is what the catalog could find, a public contract it could read. The post filed that against its own record rather than against the carriers' operations. A low score here tells you what's discoverable, and for most shipping lines nothing is.
So where do you actually start? The post's advice is practical. For voyage or fleet tooling, begin with vessel tracking (VesselFinder, MarineTraffic) and ocean weather (Tomorrow.io, Sofar Ocean), where the contracts are deepest. MarineTraffic is the only provider in the vertical with more published APIs than unpublished, 9 of 14. For booking and shipment events, Maersk is the only carrier with a published surface on the network. For class and certification data, DNV lists a Class Status API and its Vessel Register.
What you take away is a corrected picture of the sector. Maritime on APIs.io is served from the edges: weather, sensors, tracking and fleet software are published, and the shipping lines mostly are not. Treat the headline totals with suspicion, plan your integrations around the providers that actually publish, and if you ever sit on the carrier side of a developer program, notice that the bar is Maersk at 43.0 and nobody else is close.
Read the original: https://apis.io/2026/11/09/maritime-on-apis-io-the-top-score-is-a-weather-company-and-the-big-carriers-sit-in-minimal/