Datalastic · Rate Limits

Datalastic Rate Limits

Datalastic enforces two layers of limits. First, a hard request-rate cap of 600 API calls per minute applies uniformly across all subscription plans - exceeding it returns a Too Many Requests error. Second, a monthly database-credit quota meters how much data is returned - Starter includes 20,000 credits, Experimenter 80,000, and Developer Pro+ is unlimited. Credits are deducted per result, not per request - 1 per vessel or port returned, 1 per vessel per day of history, with /vessel_inradius capped at 500 vessels per call. Failed requests do not deduct credits, unused credits reset monthly, and the /stat endpoint reports current consumption for free.

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

It captures 7 rate-limit definitions, measuring requests, credits, results, vessels, and days.

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

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

7 Limits Throttle: 429
Vessel TrackingMaritimeAISRate LimitingQuotas

Limits

API Calls Per Minute api-key
requests
600 per minute
Applies to all plans; exceeding it returns a Too Many Requests error.
Starter Monthly Credits account
credits
20000 per month
One credit per vessel/port result or vessel-day of history returned.
Experimenter Monthly Credits account
credits
80000 per month
One credit per vessel/port result or vessel-day of history returned.
Developer Pro+ Monthly Credits account
credits
unlimited
No monthly credit cap; bounded in practice by the 600 calls/minute limit.
Vessels Per Radius Query request
results
500 per call
/vessel_inradius returns and charges at most 500 vessels; /inradius_history caps at 500 vessels per day.
Vessels Per Bulk Call request
vessels
100 per call
/vessel_bulk tracks up to 100 vessels per request, charging 1 credit per successfully returned vessel.
History Window request
days
31 days from the from date
/vessel_history accepts days or from/to (YYYY-MM-DD) with a 31-day maximum range.

Policies

Per-Result Metering
Credits are consumed by results returned, not by requests made; failed requests are not charged and usage checks via /stat are free.
Overuse Protection
Plans include overuse protection and credit tracking so consumption stops rather than silently overrunning the monthly quota.
Monthly Reset
Unused database credits reset at the end of each monthly billing cycle and do not roll over.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Too Many Requests responses when approaching the 600 calls/minute cap.

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