Base URL
Authentication
Most read-only endpoints are open to the public. Endpoints that return user-specific data, mutating endpoints, and high-volume reads require an API key. A small public-tier slice — the single-vessel latest-position lookup — is fully open, requires no key, ships JSON-LD attribution, and has its own OpenAPI 3.1 spec suitable for citation by journalists, academics, and AI ingestion pipelines. Pass the key via theX-API-Key header:
Access tiers
See
/api/v1/billing/plans for live pricing.
Rate limiting
Rate limit headers are returned on every response:X-RateLimit-Limit— your tier’s per-minute limitX-RateLimit-Remaining— requests remaining in the current windowX-RateLimit-Reset— UTC epoch seconds when the window resets
Retry-After header.
Response format
All endpoints return JSON with the data nested under a top-level key matching the resource (e.g.vessels, positions, events). Errors return:
Methodology
Every endpoint that returns inferred or modeled data (cargo estimates, risk scores, dark fleet detections, draft anomalies) includes:- A
confidenceortierfield indicating signal strength - A
methodologylink in the response or in the endpoint docs
Port slugs
Ports are referenced by slug (e.g.houston, santos, singapore, rotterdam). Get the full list from GET /api/v1/ports.
Quick start
SDK + MCP
- Python:
pip install axiom-overwatch— see SDKs & MCP. - MCP server: lets Claude / GPT / any MCP-compatible AI agent query Overwatch directly.
Where to from here
Browse the endpoints by category in the sidebar, or jump to the most-used groups:Vessels & Positions
Real-time AIS positions and vessel registry
Risk Intelligence
Dark fleet, STS, loitering, identity changes
Trade Flows
Bilateral commodity trade, mirror discrepancies, sanctions
Emissions
CSRD/SEC Scope 3 maritime emissions reports