Kpler · Rate Limits

Kpler Rate Limits

Kpler does not publish hard numeric rate limits for the Direct Access APIs. Instead the public documentation gives usage guidance - core endpoints (trades, vessels, flows, port calls, ship-to-ship, storage) should be queried about once per hour, and queries should be run sequentially, one after another, rather than in parallel, to reduce load. The data itself updates on platform refresh cycles, so higher polling frequencies add no information. MarineTraffic services are constrained by credit consumption per call rather than a published requests-per-minute cap. The legacy Maritime 2.0 GraphQL API (being discontinued) documented an explicit 60 requests per minute per token leaky-bucket limit, with multi-root queries counted as multiple requests.

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

It captures 4 rate-limit definitions, measuring requests, concurrent requests, and credits.

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

Tagged areas include Vessel Tracking, Maritime, Commodities, Supply Chain, and Rate Limiting.

4 Limits Throttle: 429
Vessel TrackingMaritimeCommoditiesSupply ChainRate LimitingQuotas

Limits

Direct Access Endpoint Polling endpoint
requests
guidance of 1 request per hour per core endpoint
Documented as recommended query frequency for trades, vessels, flows, port calls, ship-to-ship, and storage endpoints, not an enforced numeric cap.
Direct Access Concurrency account
concurrent requests
1 (sequential queries recommended)
Kpler asks that queries not be run simultaneously; run them one after another.
MarineTraffic Credit Consumption api_key
credits
per purchased credit balance
Each MarineTraffic service call consumes credits; the API exposes Credits Balance endpoints for monitoring.
Maritime 2.0 GraphQL Requests (legacy) token
requests
60 per minute
Leaky-bucket limit on the discontinued api.sml.kpler.com/graphql endpoint; multi-root queries count as multiple requests.

Policies

Sequential Querying
Run Direct Access queries sequentially rather than in parallel; the platform is designed for scheduled extraction, not high-frequency polling.
Hourly Refresh Alignment
Poll core endpoints at most hourly to align with platform data refresh cycles.
Backoff Strategy
Implement exponential backoff with jitter and honor Retry-After on 429 responses.

Sources

Work with this as data

Every rate limit 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 rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • 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 rate limit 
curl "https://apis.io/api/v1/rate-limits/kpler-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

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