Simple plans, no surprises

One successful call to /interpreter (HTTP 2xx), whatever its size, including answers served from our 60-second cache. Failed and rejected requests are not counted.

The height or depth of one location. A request to the elevation API can hold up to 10,000 locations and uses one lookup per location; a route profile uses one per sample point (one every 90 m by default). Lookups have their own monthly allowance and never use up Overpass requests.

Many map users need no Overpass queries, and many Overpass users need few map tiles. With two plans you pay for what you use: an account always has an Overpass plan and a Maps plan, both free until you choose a paid one. When both include elevation lookups, the larger allowance applies.

One vector tile or one terrain tile delivered to a map. Styles, fonts, icons and TileJSON are free, and so are tiles the browser already has. A full-screen map loads about 15 to 30 tiles when it opens. Map tiles have their own monthly allowance and never use up Overpass requests or elevation lookups. See the map tiles.

From OpenStreetMap, as vector tiles of the whole world built by Protomaps and updated every week, up to zoom 14. Terrain comes from the same Copernicus 90 m data as the elevation API.

Copernicus DEM GLO-90 on land (90 m grid) and the GEBCO grid at sea. See the elevation API for accuracy and the comparison with other providers.

They are the upper limits for the Overpass [timeout:…] and [maxsize:…] settings. If your query asks for more, we lower the value to the limit of your plan and tell you in the X-Effective-Timeout and X-Effective-Maxsize response headers.

Half of the server's query slots are reserved for paid plans, and a slot that frees up goes to a waiting paid query first. Free accounts share the other half and have low priority: when a free request finds no slot within a few seconds it gets HTTP 503 and should retry.

Per account. All keys of an account share the quota, rate and parallel-query limits of its plan, so you can use separate keys per app or environment without paying more.

While you evaluate and develop it, yes. A website, app or service that earns money, production use by a business and work for a paying client need a paid plan. The free plans are for personal, educational and non-profit projects. Accounts created before 27 October 2026 may keep using them commercially; see section 4 of the terms.

Upgrades and downgrades apply immediately and are prorated to the day. Cancellations take effect at the end of the period you paid for; your account then moves to the free plan and your keys keep working within its limits.

For yearly plans and custom volumes, yes. Contact us and we will set it up.

Not on the standard plans yet. We monitor the service continuously and publish its state on the status page.