Get started
API conventions

Rate limits and usage

Rate limits and usage

Limits apply per organization and per API, across every key you own. Past one, the API answers 429 Too Many Requests with a Retry-After header: wait that many seconds, then send the request again.

Default limits

APIPer minute, for your own clientsPer billing period
Data API60 requests300,000 root fields
Tile API600 tiles2,000,000 tiles
Map Studio API600 reads per IP address, then 6,000 per organizationNo allowance

An agreement may set other figures. A second publishable key adds no quota: every key of your organization shares the same limits.

What counts

Only your own clients and the hosted embed count: requests made with your keys from your servers, pages, and SDK calls, the MCP server, and the tiles the hosted embed draws. They count toward your limits, your allowance, and your invoice.

An Embedded Studio, Map Studio in the Mountaya app, and share links are recorded in your usage but never counted. The Tile API's base map is never counted either.

Read the rate-limit headers

The Data API and the Tile API report what is left of each limit on every answer, so you can slow down before a 429. Send a request with your keys and print the headers:

curl -s -o /dev/null https://data.mountaya.com/graphql \
  -H "X-API-Key: $MOUNTAYA_PUBLISHABLE_KEY" \
  -H "X-Session-Token: $MOUNTAYA_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"query": "query Directions($input: DirectionsInput!) { directions(input: $input) { routes { distance } } }", "variables": {"input": {"activity": "HIKING_AND_TRAIL", "waypoints": [[6.8712, 45.9231], [6.9271, 45.9822]]}}}' \
  -w 'RateLimit-Policy: %header{ratelimit-policy}\nRateLimit: %header{ratelimit}\n'

For example:

RateLimit-Policy: "minute";q=60;w=60, "month";q=300000;w=2678400
RateLimit: "minute";r=41;t=23, "month";r=287354;t=1036800

RateLimit-Policy names each limit with its quota q and window w in seconds. RateLimit gives, in the same order, the requests left r and the seconds until the window resets t.

Handle a 429

Wait the seconds Retry-After names, plus a little random jitter, then send the same request. A write retried with its Idempotency-Key is never made twice.

# curl waits out Retry-After on a 429 before each retry.
curl --retry 3 https://data.mountaya.com/graphql \
  -H "X-API-Key: $MOUNTAYA_PUBLISHABLE_KEY" \
  -H "X-Session-Token: $MOUNTAYA_SESSION_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"query": "query Directions($input: DirectionsInput!) { directions(input: $input) { routes { distance } } }", "variables": {"input": {"activity": "HIKING_AND_TRAIL", "waypoints": [[6.8712, 45.9231], [6.9271, 45.9822]]}}}'

A 429 for a spent monthly allowance names the seconds until your next billing period begins. Do not retry before then.

Map Studio API limits

The Map Studio API limits reads per IP address or per member, then per organization. Exports, copies, and its costliest writes, such as imports, routed segments, and agent runs, have limits of their own per member. Imports also count the requests they send the routing engine, and agent runs the bytes they are sent.

Session minting limits

POST /v1/sessions spends none of your quotas. It counts only refused requests, so a working backend never meets its limits, and up to 6,000 tokens a minute per secret key.

See your usage

Open Organization → Usage in the Mountaya app to see what each API served this month, with the hosted embed, Embedded Studio, and share links shown apart.

Next steps

Last updated