Spire Maritime · Rate Limits

Spire Maritime Rate Limits

The Spire Maritime 2.0 GraphQL API applies a per-token request quota documented as up to 60 requests per minute per token (burst 60). Each GraphQL response reports remaining quota under extensions.requestQuota with a limit string (e.g. "60 req/m (burst 60)") and a remaining count. The raw TCP AIS stream is a continuous push feed rather than a per-request API, so it is governed by contract throughput/coverage rather than an RPM limit. Exact contractual limits vary by agreement.

Spire Maritime Rate Limits is the machine-readable rate-limit profile for Spire Maritime on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests, records, and messages.

The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Vessel Tracking, AIS, Maritime, GraphQL, and Rate Limiting.

4 Limits Throttle: 429
Vessel TrackingAISMaritimeGraphQLRate LimitingQuotasThrottling

Limits

GraphQL Requests Per Minute token
requests
60 per minute (burst 60)
Reported per-response in extensions.requestQuota (limit, remaining). Documented default; may vary by agreement.
Vessels Page Size request
records
up to 1000 vessels per page
Cursor pagination via first / after (pageInfo.endCursor, hasNextPage).
Messages Page Size request
records
up to ~20000 messages per page
Historical/recent AIS message retrieval by MMSI + time range.
TCP AIS Stream Throughput account
messages
contract-defined
Continuous push stream (not per-request). Governed by licensed coverage and throughput; server-side cursor resumes after brief disconnects.

Policies

Quota Reporting
GraphQL responses expose remaining quota inline via extensions.requestQuota so clients can self-throttle.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 responses and honor any Retry-After.

Sources