Pricing

# You pay for what you publish and build.

Your price follows the itineraries and zones you keep published, and the products you build on.

Book a meeting

[Create an account](https://app.mountaya.com/registration)

Your scope

## What does your team need?

### Online Map Studio

Our online app, nothing to install

Itinerary Editor + Map Publishing: Map and publish courses as a team.

### Outdoor Platform

Outdoor infrastructure for your products

Embedded Studio: The Itinerary Editor in your product.

Data API + MCP Server, Self-serve: Activity-aware routing, terrain, search and weather.

1k

20k

50k

100k

300k

| Monthly requests | Per request | Requests | Cost |
| --- | --- | --- | --- |
| Up to 20,000 | 0.0050 € | 20,000 | 100.00 € |
| 20,001 to 50,000 | 0.0025 € | 30,000 | 75.00 € |
| 50,001 to 100,000 | 0.0020 € |   |   |
| 100,001 to 1,000,000 | 0.0015 € |   |   |
| Over 1,000,000 | 0.0010 € |   |   |

Estimated per month, excluding VAT

175.00 €

Each tier is billed at its own rate, then the tiers are added up. One MCP Server tool call is one request, and your keys run at 60 Data API requests a minute, up to 300,000 a month.

Tile API: Basemaps, terrain and weather tiles.

### Premium options

White label: Your brand on all you publish.

Support: Covered hours and response time.

### Your selection

No product selected yet.

Book a meeting

[Create an account](https://app.mountaya.com/registration)

Included

## What one agreement gives your whole team

Every agreement includes the Itinerary Editor, Map Publishing, the SDKs & Elements and keys for the Tile API. It covers your whole team, up to any seat limit it sets. Drafts are open, and publishing runs up to the limits your agreement names. Your quote adds Embedded Studio, white label, a support tier and named limits.

### Itinerary Editor

- Activity-aware routing

- Drafts, segments and zones

- Real-time collaboration

- Elevation profiles

- AI agent, on your own AI provider

- GPX and KML import

### Map Publishing

- One line of code, on any site

- Share links and public pages

- Downloads in GPX, FIT, KML and more

- Flythrough video

- Printable PDF roadbook

### Terrain and conditions

- Activities from trail running to ski touring

- Slope, aspect, weather and snow overlays

- SAC hiking grades on each segment

### SDKs & Elements

- Typed API client that never renders

- Map elements, renderer included

- Turn-by-turn navigation

- Source-available license

### Tile API

- Vector and raster tiles

- Basemaps, terrain, weather, snow, POIs

- Mountaya, Mapbox GL, MapLibre and deck.gl

### Your agreement

- Your whole team, up to any seat limit

- Named rate limits, on contract

- Availability commitment, on contract

- White label and support, as options

- Hosted in the European Union

In production

## See what you use. Hear what changes.

Self-serve or on an agreement, every organization gets the same console. It tracks your usage by the day, sends signed webhooks and emails the members who need to know.

### Usage, day by day

See each day's requests by product, operation, source and API key. Your limits sit beside them, with the day your pace reaches them.

app.mountaya.com

### Every quota on one page

Seats, published itineraries, API volume, rate limits and webhook endpoints, each beside what you use. A signed agreement raises them.

app.mountaya.com

### Webhooks that keep trying

Your systems hear when an itinerary is published or an invoice is paid. Every delivery is signed and retried for up to three days.

app.mountaya.com

### Emails each member chooses

Each member picks the emails they get, in English or French. A change to their role always reaches them.

app.mountaya.com

### 99.9% availability, in your agreement

A signed agreement can commit us to 99.9% monthly availability of the Data API and the Tile API. Planned maintenance is announced on the status page five business days ahead.

mountaya.instatus.com

[Service status](https://mountaya.instatus.com)

Use case

## 600,000 runners, one source of geospatial data: Mountaya.

![Jonathan Levy](/images/avatars/jonathan-levy.webp)

Jonathan Levy

Co-Founder & Managing Director @ Campus Coach

Instead of juggling Google Maps, Mapbox, Strava, and other providers, we made Mountaya our single source of truth for all our geospatial data. Having one centralized, end-to-end platform radically simplifies how we manage our stack and build new products.

Jonathan Levy

![Campus Coach](/images/quote-campus.webp)

## What will you publish and build first?

Bring a course or a product idea to a tailored onboarding session. Your quote follows within 2 business days.

Book a meeting

[Create an account](https://app.mountaya.com/registration)

Frequently asked questions

What counts as a published itinerary?

An itinerary is published the moment anyone outside your organization can see it. That means a map embedded on a site, an exported video, a public page, or a share link sent to one person. A race with three courses on its event site is three published itineraries. The twenty variants you rejected on the way are drafts. Republishing an updated version is the same itinerary. Zones are counted apart, against a limit of their own. A zone is published once you publish it, for a collection's embed or share link to show.

What is a quote based on?

Three things. The itineraries and zones you keep published at the same time, each with its own limit in your agreement. The Outdoor Platform products you build on: Embedded Studio and your monthly Tile API volume. And the options you add: white label and a support tier.

How do we get a quote?

Tell us what you plan to publish and build, in the form on this page. We answer within 2 business days, with a quote in euros, excluding VAT. If you would rather see it on your own ground first, ask for a scoped pilot. We load one of your real courses and walk your team through it.

Do we need a quote to start?

Not for the Data API and the MCP Server. Create an account, add a card or a SEPA direct debit mandate and pay for the requests you make. The Itinerary Editor, Map Publishing, Embedded Studio, the Tile API, white label and support start on a signed agreement, with the scope written down first.

Can we start on our own and sign an agreement later?

Yes. The agreement covers the organization you already run, with the same keys. It adds the products it names, and can add named rate limits and an availability commitment.

How long does an agreement run?

A signed agreement runs for the term it states, twelve months unless agreed otherwise. Neither side ends it for convenience during that term. It names what it covers: your published itineraries and zones, the Outdoor Platform products you use, your rate limits and your support tier. The self-serve Data API runs month by month, each month counted from the day it opened. A failed renewal payment is retried for up to seven days, then the Data API closes. A first invoice that fails closes it at once. To open it again, add a payment method or reopen it in the billing settings. Every unpaid invoice is charged first, and nothing opens while one stays unpaid.

How is API usage counted?

The Data API counts one request per operation it answers without an error. A call that batches several operations counts each one, and an MCP Server tool call counts as one Data API request. Each month's requests are billed at the rates on this page, counted from the day the Data API opened, the month's last day included. The Tile API counts one unit per overlay or content tile served, never a basemap tile. Your agreement names its monthly volume and rate limits. Your own integration counts, Map Publishing included: the requests your servers, pages and apps make with your keys, and the MCP Server's. You see the volume of the tiles Map Publishing draws on your sites apart. Map Studio, Embedded Studio and share links are recorded apart too, and never count toward your rate limits, your monthly volume or your bill. Throttled and failed responses are never billed and never counted.

Do the SDKs & Elements need an agreement of their own?

No. The SDKs & Elements are source-available and need no agreement of their own. Their Data API requests are billed like any other, and their Tile API requests count toward your agreement.
