Data API
Routes and terrain data, one typed call away
The Data API returns routes, loop suggestions and terrain analysis anywhere in the world, as typed data for your product and your AI agents. Self-serve: create an account, add a payment method and pay per request.
Works with the tools you already use
Activity-aware outdoor data
Every route comes back measured
Ask for a route by sport, distance and climb. Each candidate comes back with its distance, its ascent, a duration paced over the ground, the surface per stretch on foot and by road bike, and the line as GeoJSON. The typed client writes the query for you.
- Routing, directions and route suggestions
- Coming soon: historical, live and forecast weather
- Elevation, terrain analysis, search and points of interest
// Three trail loops from Chamonix: about 14 km, 600 m of climbing.
const { routes } = await client.data.suggestions({
activity: "HIKING_AND_TRAIL",
start: [6.8712, 45.9231],
distance: 14000,
ascent: 600,
candidates: 3,
});
// Closest first: 13.8 km, +615 m, measured on the loop itself.
const loops = routes.map((route) => ({
distance: route.distance, // meters
ascent: route.elevation.ascent, // meters
duration: route.duration, // seconds, paced over slope and surface
surfaces: route.analysis.surfaceInfo, // surface per stretch
geometry: route.geometry, // GeoJSON, ready for your map
seed: route.seed, // send it back to keep or skip this loop
}));What your code asks
Every operation, as a typed method
Each one is a method on the typed client. Its arguments and its answer are typed from the schema.
Route suggestions
Send a sport, a distance, an ascent and a start point. Candidate routes come back as GeoJSON.
Directions
Activity-aware routes on foot, on snow and by road bike, costed on slope. Distance and duration come back with the line.
Line analysis
Send any line your users draw or import. Get its profile, ascent, descent, gradient, surface and travel time.
Terrain sampling
Elevation, slope and aspect at any set of points, or on a grid across a bounding box.
Isochrones and matrices
Reachable areas from any point as GeoJSON polygons, and time and distance matrices between points.
Search and geocoding
Geocoding, and one full-text search across places, points of interest, ways and your own itineraries.
Reverse geocoding
The nearest named place to a coordinate, with its distance. A label for any position your app shows.
Itineraries and exports
Read an itinerary by id, with its segments and waypoints. Export it as a route file at a short-lived URL.
AI agents and API
The questions your product asks every day
Ask in plain language through the MCP Server, or call the typed client. The Data API answers.
AI agent
Suggest three trail-running loops from Chamonix, around 14 km with 600 m of climbing.
{ activity: 'HIKING_AND_TRAIL', candidates: 3, distance: 14000, ascent: 600, start: [6.8712, 45.9231] }
3 loops · closest 13.8 km / +615 m
Three loops from Chamonix, each close to 14 km and +600 m. The tightest lands at 13.8 km with 615 m of climbing. Every candidate returns with full GeoJSON geometry, an elevation profile, and its surface breakdown.
Trace the fastest trail line from Chamonix to Argentière and tell me what's underfoot.
{ activity: 'HIKING_AND_TRAIL', waypoints: [[6.8712, 45.9231], [6.9271, 45.9822]] }
9.0 km · ~2h40 · asphalt → ground → gravel
A 9.0 km trail line up the valley to Argentière, about 2h40 on foot. It leaves town on asphalt, then runs on natural ground and gravel singletrack. Full GeoJSON geometry and the surface breakdown come back with it.
Break down the surface and gradient of this drawn segment before I send runners on it.
{ activity: 'HIKING_AND_TRAIL', coordinates: [[6.87126, 45.92307], [6.8713, 45.9231], …] }
+984 m · 19.9° max · asphalt → ground → compacted gravel
The segment climbs 984 m to a high point of 2,021 m with a 19.9° max gradient, a long, sustained pitch. Surface moves from asphalt to natural ground to compacted gravel, way type from street and footway, with steps, to path, then track.
Autocomplete every 'Col du' around Chamonix, with coordinates for each.
{ query: 'Col du', targets: { places: true }, focus: [6.8712, 45.9231], limit: 5 }
5 places · Brévent, Belvédère, Mont Lachat, Passon, Chardonnet
Five passes near Chamonix: Col du Brévent [6.844, 45.941], Col du Belvédère [6.876, 45.990], Col du Mont Lachat [6.796, 45.868], Col du Passon [6.983, 45.976], and Col du Chardonnet [7.012, 45.966] on the Swiss border. Each with its OSM reference and admin context.
Find the Refuge du Goûter and confirm which one is the current hut.
{ query: 'Refuge du Goûter', limit: 3 }
3 matches · Goûter Refuge (alpine_hut)
Three matches on the Goûter ridge above Les Houches: the current Goûter Refuge, tagged alpine_hut, at [6.831, 45.851], plus the historic Refuge d'Hiver and the Ancien Refuge du Goûter. Returned with OSM reference, layer, and full admin path.
How much ground can a runner cover on foot from the Chamonix aid station in 30, 60, and 120 minutes?
{ activity: 'HIKING_AND_TRAIL', locations: [[6.8712, 45.9231]], range: [1800, 3600, 7200], rangeType: 'TIME' }
3 polygons · 3.6 / 9.0 / 24.2 km² · reach 0.29 → 0.12
Reachable ground from the aid station: 3.6 km² within 30 minutes, 9.0 km² within an hour, and 24.2 km² within two. Each ring returns as a GeoJSON polygon, ready to overlay on the course.
Give me the on-foot travel-time grid between our four aid stations for the ops plan.
{ activity: 'HIKING_AND_TRAIL', locations: [[6.8712, 45.9231], [6.9271, 45.9822], …], metrics: ['DURATION', 'DISTANCE'] }
4×4 grid · Chamonix → Argentière 9.0 km
Full grid returned. Chamonix to Argentière is 9.0 km on foot; Les Houches to Le Tour, the two ends of the valley, is the longest leg on the grid. Durations in seconds, distances in meters, unreachable pairs flagged.
Use case
Terrain and weather on one map, from Mountaya.
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

What does your product need to know about the ground?
Create an account and add a payment method, and your keys open the Data API, billed per request. The docs take you to a first call.
Frequently asked questions
The Data API answers questions about outdoor ground: routes, suggestions, elevation, surface, search and geocoding, with weather coming soon. It is the engine Map Studio runs on, open to your product and your AI agents.
Three ways in. Install the typed client SDKs in your own code, with GraphQL as the wire format. Connect Claude, Cursor or any MCP client to the remote MCP Server. Or let the open-source Agent Skills teach 30+ AI coding agents to write that code.
Directions on foot, on snow and by road bike: trail, road running, road cycling, ski touring, cross-country skiing and snowshoe. Route suggestions from a brief, elevation and surface analysis along a line, isochrones, time and distance matrices, geocoding and outdoor points of interest. Historical, live and forecast weather is coming soon. Gravel and mountain biking are not available.
The Data API is self-serve and billed per request. Create an account, add a card or a SEPA direct debit mandate, and each month you pay for the requests you made, on graduated tiers. The pricing page lists every rate.
Yes, on contract. A self-serve account runs at the default limits of 60 Data API requests a minute and 300,000 a month. A signed agreement can add named rate limits and an availability commitment.