Planisfy
Guides

Rate Limits and Quotas

Understand runtime rate-limit headers, monthly quota headers, and managed versus self-host behavior.

Rate Limits and Quotas

Authenticated service requests are checked against runtime rate limits and monthly usage quotas.

Headers

The API can emit:

X-RateLimit-Limit
X-RateLimit-Remaining
X-RateLimit-Reset
Retry-After
X-Quota-Limit
X-Quota-Used
X-Quota-Remaining

Store these headers in client logs when diagnosing traffic spikes.

Failures

Rate-limit failures return:

429 RATE_LIMITED

Monthly quota failures return:

429 QUOTA_EXCEEDED

Retry rate-limit failures only after Retry-After or X-RateLimit-Reset.

Managed and self-host behavior

In managed Planisfy, hosted subscription plans can also gate features such as audit logs, operations controls, routing builds, external root agents, and planet-scale builds.

In self-host mode, hosted checkout and managed subscription gates are disabled. Usage remains visible for operational monitoring, while hosted plan quotas use the platform allowance instead of blocking self-host operators. Apply custom limits outside the built-in hosted billing workflow if your deployment needs them.

Publish a Style

Create, edit, publish, and integrate MapLibre style URLs from Planisfy Console.

Upload a Tileset

Upload or import data, build a tileset, publish TileJSON, and use the result in styles.

On this page

Rate Limits and QuotasHeadersFailuresManaged and self-host behaviorWhat to read next