Spire Maritime · FinOps Profile

Spire Maritime Finops

FinOps view of Spire Maritime spend. Spire Maritime is sold via enterprise / contact-sales agreements, not public usage-based rates, so cost is driven by the licensed data products (vessels, messages, port events, predicted ETA, historical extracts), the coverage (satellite + terrestrial AIS), the delivery channels used (GraphQL API and/or the raw TCP AIS stream), and the contracted request/throughput scope - typically a committed annual subscription rather than metered per-call billing. No public per-unit prices are asserted here.

Spire Maritime Finops is the FinOps profile for Spire Maritime on the APIs.io network, aligned with the FinOps Foundation Framework.

It defines 4 billable meters, billed in USD, on a annual cycle, and pricing category subscription-based.

The profile maps 8 FOCUS columns for cost-allocation reporting.

Tagged areas include Vessel Tracking, AIS, Maritime, Satellite AIS, and FinOps.

Category: Data and Analytics Pricing: Subscription-Based Billing: Annual FOCUS v1.3
Vessel TrackingAISMaritimeSatellite AISFinOpsCost ManagementFOCUS

Framework Alignment

Framework
Data Spec

Charge Categories

PurchaseUsageAdjustment

FOCUS Columns

BillingCurrency
USD
ChargeCategory
Purchase
InvoiceIssuerName
Spire Global
PricingCategory
Subscription-Based
ProviderName
Spire Global
PublisherName
Spire Global
ServiceCategory
Data and Analytics
ServiceName
Spire Maritime

Meters

data_subscription
Unit: contract
Committed annual license to Spire Maritime data products (contract-defined scope). No public per-unit rate.
graphql_requests
Unit: requests
Maritime 2.0 GraphQL requests (quota ~60 req/min per token); usage governed by agreement, not public per-call price.
stream_throughput
Unit: messages
Real-time AIS messages delivered over the raw TCP stream; scoped by licensed coverage/throughput.
historical_extracts
Unit: datasets
Custom historical AIS / events data extracts delivered as datasets.

Sources