Ship the outdoors
For developers and apps
Outdoor intelligence, one prompt away.
The engine behind Map Studio, ready for your AI agents and apps: a remote MCP server, open-source Agent Skills, and a typed GraphQL API. Activity-aware routing, weather, terrain, and isochrones, ready to drop into your product.
Works with the tools you already use
Challenges we solve
Ship outdoor routing, weather, and terrain without building the stack.
Ship in days, not quarters
Building the outdoor stack means months on data sourcing, tiling, and routing before you write a line of product. Mountaya is that whole stack behind one API, so you launch on top of it.
Outdoor-native, not repurposed road tech
Most geospatial APIs are built for cars and cities. Mountaya is activity-aware across nine sports, with surface, slope, snow, and per-meter elevation the outdoors actually needs.
One engine for your app and your agents
Serve the same routing, weather, and terrain to your product and your AI agents: typed GraphQL for your code, a remote MCP server and Agent Skills for Claude, Cursor, and 30+ agents.
Data API
One endpoint, the whole mountain
Ask for a route, an isochrone, a matrix, or the weather on a segment, and get exactly the fields you requested back. The schema is typed and introspectable, so your agents discover it without reading a page of docs.
- Routing, directions, and route suggestions
- Weather: historical, live, and forecast
- Elevation, terrain, search, and POIs
Ways to connect
Three ways to reach outdoor data
Connect your AI agents and apps to the same outdoor data engine through a remote MCP server, open-source Agent Skills, or a typed GraphQL API.
Claude
ChatGPT
Cursor
WindsurfMCP server
Connect Mountaya to Claude, Cursor, and any MCP client. Remote, hosted, always current.
Agent Skills
Open-source skills that let any AI coding agent authenticate, discover our data, and query Mountaya in natural language. No docs to read, no queries to write.
GraphQL API
A strictly typed, introspectable GraphQL API. Fetch exactly the routes, weather, elevation, and POIs your app needs.
Agents & API
The questions your product asks every day
Connect through an MCP server, Agent Skills, or GraphQL, and ask in plain language. Outdoor Intelligence answers.
Generate 3 ski touring loops, 18 km, 1200 m ascent, from Courmayeur.
3 routes · geometry + elevation returned
Returns three route geometries with surface breakdown and elevation profile in a single query.
Reachable area on foot from this rescue base in 30, 60, and 120 minutes.
3 polygons · 9.1 / 22.4 / 60.1 km²
Returns three polygons with reach factor, ready to overlay on your map.
For each of these rescue GPS pings, name the closest hut or trailhead.
Montenvers - Mer de Glace · bus_stop
Each ping resolves to its nearest named place with distance in meters, so dispatch can call in a landmark, not a raw coordinate.
Outdoor-native, Mapbox-compatible
Outdoor Tiles serve the Mapbox GL and MapLibre renderers you already run. Swap the tile URL, keep your stack, and gain terrain, weather, and snow layers built for the outdoors.
Compare Mountaya vs. MapboxWhy outdoor teams switch to Mountaya
- Stitching weather, terrain, and elevation from five vendors
- Road-network routing that sends trail users onto highways
- Building and hosting your own tile pipeline
- Hand-written glue code for every AI agent
- One typed GraphQL API for routing, weather, terrain, and elevation
- Activity-aware routing across nine outdoor activities
- Drop-in vector and raster tiles for Mapbox GL and MapLibre, 99.9% SLA
- A remote MCP server and Agent Skills your agents use out of the box
Use case
How Campus Coach empowers 600,000 runners with unified terrain and weather maps from Mountaya, for greater training impact.
The depth of Mountaya's mapping ecosystem transforms the experience on our mobile apps. By integrating their contextual data, we give our users the terrain insight they need to anticipate and prepare their races in the best possible conditions.
Jonathan Levy
Pricing
Pricing built around how you map
| Monthly requests | Per request | Per 1,000 |
|---|---|---|
| Up to 20,000 | 0.0050€ | 5.00€ |
| 20,001 to 50,000 | 0.0025€ | 2.50€ |
| 50,001 to 100,000 | 0.0020€ | 2.00€ |
| 100,001 to 1,000,000 | 0.0015€ | 1.50€ |
| Over 1,000,000 | 0.0010€ | 1.00€ |
Tiered pricing: each tier of your monthly usage is billed at its own rate, then added together.
Prices in euros, VAT excluded. Usage is billed monthly, at the end of each billing period.
| Monthly requests | Per request | Per 1,000 |
|---|---|---|
| Up to 200,000 | 0.00050€ | 0.50€ |
| 200,001 to 500,000 | 0.00025€ | 0.25€ |
| 500,001 to 1,000,000 | 0.00020€ | 0.20€ |
| Over 1,000,000 | 0.00010€ | 0.10€ |
Tiered pricing: each tier of your monthly usage is billed at its own rate, then added together.
Prices in euros, VAT excluded. Usage is billed monthly, at the end of each billing period.
Built for outdoor apps and platforms embedding Map Studio for their users, billed per seat plus API usage.
150€/month
1 × 150€/seat · month
Frequently asked questions
Usage-based, per request, with volume rates that decrease as you scale. The full rate table is public on the pricing page.
Yes. Use the remote MCP server or the open-source Agent Skills. Both work with Claude, Cursor, and any client that supports the standard formats.
Yes. Enterprise customers get custom integrations, SSO, and dedicated support.