Home
Providers
Spire Maritime
Spire Maritime
Spire Maritime (Spire Global) delivers satellite and terrestrial AIS vessel data - global ship positions, static vessel characteristics, voyage and destination data, port events, and predicted ETAs. The flagship Maritime 2.0 service is GraphQL-first at a single endpoint (https://api.spire.com/graphql, Bearer token auth), with a separate raw-TCP AIS stream for real-time message delivery in NMEA 0183 format. Access is enterprise / contact-sales. NOTE - following Spire Maritime's acquisition by Kpler, these APIs are being migrated/discontinued; new integrations are directed to developers.kpler.com.
Spire Maritime publishes 1 API on the APIs.io network: Vessels API. Tagged areas include Vessel Tracking, AIS, Maritime, Satellite AIS, and Ship Tracking.
Spire Maritime’s developer surface includes authentication, documentation, and 7 more developer resources.
5 APIs
On this page
Kin Score
APIs 5
Open Collections 1
Pricing Plans 1
Rate Limits 1
FinOps 1
Security Posture 2
Resources 9
apis.yml
34 Operational Transparency
Composite quality — 33.6/100 · thin
Agent readiness — 18/100 · agent aware
Individual APIs this provider publishes, each with its own machine-readable definition.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Published pricing tiers and plan structures.
Documented rate limits and quota policies.
Cost, billing, and metering signals for API financial operations.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Source (apis.yml)
aid: spire-maritime
url: https://raw.githubusercontent.com/api-evangelist/spire-maritime/refs/heads/main/apis.yml
name: Spire Maritime
kind: company
description: Spire Maritime (Spire Global) delivers satellite and terrestrial AIS vessel data - global ship positions, static
vessel characteristics, voyage and destination data, port events, and predicted ETAs. The flagship Maritime 2.0 service
is GraphQL-first at a single endpoint (https://api.spire.com/graphql, Bearer token auth), with a separate raw-TCP AIS stream
for real-time message delivery in NMEA 0183 format. Access is enterprise / contact-sales. NOTE - following Spire Maritime's
acquisition by Kpler, these APIs are being migrated/discontinued; new integrations are directed to developers.kpler.com.
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: enterprise
onboarding: self-serve
trial: false
try_now: false
public: false
label: Enterprise · Self-serve signup
confidence: high
source:
- plans
- authentication
- url: https://spire.com/maritime/
status: 301
note: declared website redirects to https://www.kpler.com/product/maritime/kplerais — a different registrable domain (spire.com
-> kpler.com), possible rename or acquisition (probed 2026-09-03, roadmap#169)
generated: '2026-07-22'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/spire-maritime.png
tags:
- Vessel Tracking
- AIS
- Maritime
- Satellite AIS
- Ship Tracking
- Real-Time Data
- Maritime Data
- Predicted ETA
- Port Events
- Location
- GraphQL
created: '2026-07-12'
modified: '2026-07-12'
specificationVersion: '0.23'
apis:
- aid: spire-maritime:spire-maritime-vessels-api
name: Spire Maritime Vessels API
tags:
- Vessels
- AIS
- Ship Tracking
- GraphQL
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://documentation.spire.com/maritime-2-0/
baseURL: https://api.spire.com/graphql
properties:
- url: https://documentation.spire.com/maritime-2-0/
type: Documentation
- url: https://documentation.spire.com/maritime-2-0/#graphql
type: APIReference
- url: graphql/spire-maritime.graphql
type: GraphQL
- url: collections/spire-maritime.postman_collection.json
type: PostmanCollection
- url: collections/spire-maritime.opencollection.json
type: OpenCollection
description: GraphQL `vessels` query returning up to 1,000 vessels per page - static data (name, MMSI, IMO, callsign, flag,
shipType, dimensions), last position update (lat/long, course, heading, speed, collectionType SATELLITE or TERRESTRIAL),
current voyage (destination, draught, ETA, matched port), and extended vessel characteristics. Filter by MMSI/IMO/callsign/flag/shipType,
area of interest (GeoJSON/WKT polygon), or last-position time range; cursor pagination via first/after.
- aid: spire-maritime:spire-maritime-messages-api
name: Spire Maritime Messages API
tags:
- Message
- AIS
- Historical AIS
- GraphQL
tags_raw:
- Messages
- AIS
- Historical AIS
- GraphQL
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://documentation.spire.com/maritime-2-0/
baseURL: https://api.spire.com/graphql
properties:
- url: https://documentation.spire.com/maritime-2-0/
type: Documentation
- url: graphql/spire-maritime.graphql
type: GraphQL
description: GraphQL query surface for decoded AIS messages (position and static/voyage reports) filtered by MMSI and time
window, returned in large paginated batches. Used to pull recent and historical AIS message history over HTTPS rather
than the always-on TCP stream. Message-level field selection here is representative and grounded in Spire's documented
message model.
- aid: spire-maritime:spire-maritime-port-events-api
name: Spire Maritime Port Events API
tags:
- Port Events
- Port Calls
- Maritime
- GraphQL
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://documentation.spire.com/maritime-2-0/#port-events
baseURL: https://api.spire.com/graphql
properties:
- url: https://documentation.spire.com/maritime-2-0/#port-events
type: Documentation
- url: graphql/spire-maritime.graphql
type: GraphQL
description: GraphQL port-event queries - `portEventsByVessel`, `portEventsByLocation`, and `portEventsByShipType` - surfacing
vessel arrivals and departures (ATA/ATD), port calls, and berth/anchorage events with state filtering. Backed by an improved
event algorithm for more accurate arrival/departure recognition.
- aid: spire-maritime:spire-maritime-predicted-eta-api
name: Spire Maritime Predicted ETA / Routing API
tags:
- Predicted ETA
- Routing
- Voyage
- GraphQL
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://documentation.spire.com/routing-api/
baseURL: https://api.spire.com/graphql
properties:
- url: https://documentation.spire.com/routing-api/
type: Documentation
- url: graphql/spire-maritime.graphql
type: GraphQL
description: Predicted vessel routing and ETA - a `predictedVesselRoute` query taking an origin, destination, and vessel
and returning the predicted sea route, distance, and estimated time of arrival / voyage duration. Complements the self-reported
AIS ETA in currentVoyage with a computed, ocean-network ETA.
- aid: spire-maritime:spire-maritime-ais-tcp-stream
name: Spire Maritime AIS TCP Stream
tags:
- Real-Time Data
- Streaming
- AIS
- NMEA 0183
- TCP
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/apis-json-logo.jpg
humanURL: https://documentation.spire.com/tcp-stream-v2/using-the-tcp-stream/
baseURL: streamingv2.ais.spire.com:56784
properties:
- url: https://documentation.spire.com/tcp-stream-v2/using-the-tcp-stream/
type: Documentation
description: Always-on real-time AIS feed delivered over a RAW TCP SOCKET (not HTTP, not WebSocket). Client opens a TCP
connection to streamingv2.ais.spire.com port 56784, authenticates with a token, and receives encoded AIS sentences in
NMEA 0183 v4.0 with a timestamp TAG-block prefix, one sentence per line. A server-side cursor resumes the stream after
brief disconnects. This is a plain TCP transport - there is NO documented WebSocket (wss://) endpoint.
common:
- type: DomainSecurity
url: security/spire-maritime-domain-security.yml
- type: Authentication
url: authentication/spire-maritime-authentication.yml
- type: GitHubOrganization
url: https://github.com/spireglobal
- type: LinkedIn
url: https://www.linkedin.com/company/spire-global
- type: Website
url: https://spire.com/maritime/
- type: Documentation
url: https://documentation.spire.com/
- type: Plans
url: plans/spire-maritime-plans-pricing.yml
- type: RateLimits
url: rate-limits/spire-maritime-rate-limits.yml
- type: FinOps
url: finops/spire-maritime-finops.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
Every provider here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for providers
9 MCP tools reach this
find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.
All 92 tools →
Call it yourself
curl for this page
This provider
curl "https://apis.io/api/v1/providers/spire-maritime"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/spire-maritime/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/spire-maritime/evidence"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms .
A second provider on the same verified email joins the account you already have.