Vake
VAKE is a Norwegian maritime domain awareness company that detects, identifies, and tracks "dark vessels" from space. The VAKE platform fuses satellite imagery, AIS signals, and machine learning to reveal hidden vessel activity at sea for governments and industry. Its three products are Pathfinder, which reconstructs a vessel's past, present, and predicted movements and searches satellite imagery for vessels that go AIS-dark; Overwatch, which monitors an Area of Interest around ports, critical infrastructure, and economic zones to surface unreported activity such as illegal fishing, transshipments, and spoofing; and Clearview, a machine-learning service that identifies dark-vessel observations in multispectral satellite imagery against a global vessel-signature database spanning 2016 to today. The platform is delivered as a web application (studio.vake.ai) backed by a private API (api.nemme.io); onboarding is sales-led rather than self-serve.
Vake is profiled on the APIs.io network. Tagged areas include Company, Maritime, Maritime Domain Awareness, Satellite Imagery, and Vessel Tracking.
Vake’s developer surface includes documentation, getting-started guide, support, and 5 more developer resources.
Kin Score
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.
| Market | Position | Depth | Registered MCP server | Declares compatibility |
|---|---|---|---|---|
| Maritime Logistics (ocean shipping, eBL, ports) | undeclared | - | - | - |
Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards implemented 1
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Security Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 2
The organization behind the API
Source (apis.yml)
Work with this as data
Every provider here is available over the APIs.io API and to AI agents over MCP.