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 is listed with 5 APIs on the APIs.io network, including Vessels API, and 4 more. 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.

🌐 Visit website 📡 Profile data on GitHub

15.7/100 emerging ▬ flat Agent 3/100 human only Heartbeat 21/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessEnterprise

5 APIs

Vessel Tracking AIS MaritimeSatellite AISShip Tracking Real-Time Data Maritime DataPredicted ETAPort EventsLocation GraphQL

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 15.7/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 5.6 / 17

Access Clarity 0.9 / 17

Operational Transparency 1.2 / 11

Contract Governance 0.0 / 10

Discoverability 6.1 / 9

Regulatory Posture 1.8 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/spire-maritime/"><img src="https://apis.io/badge/spire-maritime/card.svg" alt="Spire Maritime on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

Machine-Readable Contract +18 pts — api_specs includes an OpenAPI document
MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

11 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 0.0 — up to +25.0 composite points
Access Clarity scores 5.3 — up to +18.9 composite points
Developer Ergonomics scores 32.9 — up to +13.4 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/spire-maritime/apis.yml: open an issue on github.com/api-evangelist/spire-maritime to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

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	-	-	-
Space and Satellite (operators, earth observation, ground segment)	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 3

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.

AIS

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

GraphQL

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

Postman Collections

measured — observed by APIs.io (published)

APIs 5

Individual APIs this provider publishes, each with its own machine-readable definition.

Spire Maritime Vessels API

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, hea...

Spire Maritime Messages API

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 an...

Spire Maritime Port Events API

GraphQL port-event queries - `portEventsByVessel`, `portEventsByLocation`, and `portEventsByShipType` - surfacing vessel arrivals and departures (ATA/ATD), port calls, and berth...

Spire Maritime Predicted ETA / Routing API

Predicted vessel routing and ETA - a `predictedVesselRoute` query taking an origin, destination, and vessel and returning the predicted sea route, distance, and estimated time o...

Spire Maritime AIS TCP Stream

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...

Open Collections 1

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

Spire Maritime 2.0 (GraphQL)

OPEN COLLECTION

Spire Maritime API pricing

Not yet checked against Spire Maritime's own pricing page. Compiled by API Evangelist on 2026-07-12 from spire.com/maritime/; confirm before you rely on a figure.

Plan	Price
Enterprise / Contact Sales enterprise	—

Plan details, limits and sources →

Rate limits

GraphQL Requests Per Minute: 60 per minute (burst 60) requests
Vessels Page Size: up to 1000 vessels per page records
Messages Page Size: up to ~20000 messages per page records

Compiled by API Evangelist, not yet checked against Spire Maritime's documentation. All 4 limits →

Pricing Plans 1

Published pricing tiers and plan structures.

Spire Maritime Plans Pricing

1 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Spire Maritime Rate Limits

4 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Spire Maritime Finops

FINOPS

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Spire Maritime Authentication

http/token · 2 schemes

SECURITY

Spire Maritime Domain Security

TLSv1.3 · DMARC

SECURITY

Resources

Documentation 1

Reference material describing how the API behaves

Documentation

Documentation

Build 1

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Access & Security 2

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Authentication

Authentication

Operate 1

Status, limits, changes, and where to get help

RateLimits

RateLimits

Commercial 2

Pricing, plans, and the legal terms of use

Plans

Plans

FinOps

FinOps

Company 2

The organization behind the API

LinkedIn

Website

Website

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: unknown
  trial: false
  try_now: false
  public: false
  label: Enterprise
  confidence: medium
  source:
  - plans
  - authentication
  - security
  - 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-11-06'
  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
x-parent: spire-global
x-relationship: product

Spire Maritime API — frequently asked questions

Does Spire Maritime have an API?

Yes. APIs.io lists 5 APIs from Spire Maritime, including Spire Maritime Vessels API, Spire Maritime Messages API and Spire Maritime Port Events API, and 2 more.

How do I authenticate with the Spire Maritime API?

Spire Maritime uses bearer-token authentication (http/token · 2 schemes). The details are profiled on APIs.io as Spire Maritime Authentication.

How much does the Spire Maritime API cost?

APIs.io lists 1 pricing plan for Spire Maritime, with each plan's price, limits and inclusions under Pricing on this page.

Is the Spire Maritime API ready for AI agents?

Spire Maritime has a Kin Score of 15.7 out of 100 (emerging) and an Agent Readiness score of 3.1 (human-only), scored by API Evangelist on 2026-11-06.

Work with this as data

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"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.