Radar Io Rate Limits
Radar enforces per-organization rate limits on the api.radar.io/v1 REST API, expressed primarily as requests per second, and separately meters monthly API-call and tracked-user quotas by plan. Server (secret key) endpoints such as track, geofence management, and users have their own limits distinct from client (publishable key) endpoints such as geocoding, search, and routing. Specific per-endpoint values are set per organization and plan and are not reconciled in this artifact.
Radar Io Rate Limits is the machine-readable rate-limit profile for Radar on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 4 rate-limit definitions, measuring requests and users.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Location, Geocoding, Geofencing, Maps, and Routing.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/radar-io-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.