Sinay is a maritime data and analytics company whose Developers Platform exposes a marketplace of REST APIs for the shipping and ocean-tech industry - vessel and port lookup from combined satellite and terrestrial AIS, metocean (weather and ocean) conditions, per-voyage CO2 emissions modeled on the GLEC Framework, ETA prediction, live port congestion, sailing schedules, and underwater noise.
APIs.json: https://raw.githubusercontent.com/api-evangelist/sinay/refs/heads/main/apis.yml
- Marketplace of per-product REST APIs. Every Sinay API is served over HTTPS from the single host
api.sinay.ai, with each product mounted under its own versioned base path - e.g.https://api.sinay.ai/co2/api/v2andhttps://api.sinay.ai/ports-vessels/api/v1. - One auth scheme everywhere. All endpoints require an API key sent in an
API_KEYrequest header. Get a free key from the Sinay Developers Platform. - Per-API subscriptions / credits. Usage is metered as monthly API calls / API units (credits). Published tiers: a Free plan (~500 calls/month), a Pro plan (~10,000 calls/month), and a custom Enterprise plan, plus a no-credit-card free trial (~100 calls/month). Some endpoints consume more than one API unit per call. Each API reports its own consumption via a
/usagesendpoint (or/consumptionon Port Congestion). Prices/currency are not reconciled here - confirm on the Developers Platform. - REST only. No public WebSocket API is documented. A separate Webhooks API (container-tracking / Safecube surface) pushes events via HTTP POST to a subscriber endpoint; it is out of scope for the five maritime APIs profiled here.
This entry profiles five of Sinay's maritime-data APIs. The Swagger index at api.sinay.ai/doc also lists live specs for underwater noise, sailing schedules, Safecube Ports Intelligence (beta), container tracking, webhooks, and Safecube - not profiled separately here.
- Vessel Tracking
- AIS
- Maritime
- Maritime Data
- Weather
- CO2 Emissions
- Port Congestion
- Ship Tracking
- ETA
- Ocean Data
- Created: 2026-07-12
- Modified: 2026-07-12
Look up vessels by name, MMSI, or IMO and ports by name or UN/LOCODE from Sinay's maritime reference data, built on combined satellite and terrestrial AIS.
- Human URL: https://sinay.ai/en/sinay-hub/ports-and-vessels-api/
- Base URL:
https://api.sinay.ai/ports-vessels/api/v1 - Endpoints:
GET /vessels,GET /ports,GET /usages
Retrieve meteorological and oceanographic (weather and ocean) conditions for a geographic area and time window from a chosen model.
- Human URL: https://sinay.ai/en/sinay-hub/metocean-api/
- Base URL:
https://api.sinay.ai/metocean/api/v1 - Endpoints:
GET /models,POST /stations,GET /usages
Compute the CO2 emissions of a container voyage between two ports for a given vessel (IMO or MMSI), returning voyage length and tons of CO2 per TEU via a vessel-model method and a GLEC Framework tradelane method (WTT/TTW/WTW).
- Human URL: https://sinay.ai/en/sinay-hub/co2-api/
- Base URL:
https://api.sinay.ai/co2/api/v2 - Endpoints:
POST /compute-co2,GET /usages
Predict a vessel's estimated time of arrival to a destination port, routed from its latest AIS position or from a specified departure port and date.
- Human URL: https://sinay.ai/en/sinay-hub/eta-api/
- Base URL:
https://api.sinay.ai/etac/api/v1 - Endpoints:
POST /compute-eta,GET /usages
Retrieve aggregated live port congestion data for a single port by UN/LOCODE or up to ten ports at once, plus credit-consumption reporting.
- Human URL: https://sinay.ai/en/sinay-hub/port-congestion-api/
- Base URL:
https://api.sinay.ai/congestion/api/v1 - Endpoints:
GET /congestion/{portCode},POST /congestion/batch,GET /consumption/current-period,GET /consumption/periods
- OpenAPI - consolidated description of all five APIs
- Postman Collection
- Open Collection
- Authentication
- Plans
- Rate Limits
- FinOps
- Domain Security
- Review
- Endpoints, methods, the
API_KEYheader security scheme, and the CO2 / ETA / congestion request-response shapes were transcribed from the live per-product Swagger files athttps://api.sinay.ai/<product>/api/<version>/swagger.yaml(confirmed 2026-07-12). - In the consolidated OpenAPI, some response bodies (vessel/port records, metocean stations, ETA result, congestion aggregate) are represented as generic objects; the authoritative field-level schemas live in the upstream per-product Swagger.
- Pricing (
plans,finops) is modeled from public descriptions of the Developers Platform and markedreconciled: false; per-unit prices, currency, and per-endpoint credit weightings are unverified.
FN: Kin Lane Email: kin@apievangelist.com