Agent skills
Drop-in agent skills that teach AI coding assistants how to use Mountaya: authentication, the Data API, the Tile API, and Map Embedding.
Mountaya publishes a set of agent skills in the mountayaapp/agent-skills repository. Each skill is a focused package of instructions (and, for some, helper scripts) that an AI assistant loads on demand. Install them once and your agent knows how to authenticate, compute routes, render tiles, and embed the studio without you pasting docs into the chat.
If you want an agent to call the Data API directly over a live protocol instead of generating client code, see the MCP server, which exposes the same Data API as read-only MCP tools.
Skills
mountaya-authAPI authentication: publishable keys, session tokens, and rate limits. This is the prerequisite skill; the Data API skill depends on it for session-token creation.
mountaya-data-apiThe Data API for outdoor routing and geospatial analysis: directions, suggestions, isochrones, matrices, geocoding, POIs, and geometry analysis. Requires mountaya-auth.
mountaya-tiles-apiThe Tile API: rendering overlays, itineraries, and collections with MapLibre GL JS.
mountaya-embeddingMap Embedding: iframe integration, parameters, postMessage events, and safety rules.
Install
The skills install from the public repository. The CLI is the recommended path; manual copying works for any tool that reads a skills directory.
Install the whole set, or pass --skill to install one at a time. mountaya-data-api depends on mountaya-auth, so install both when you use the Data API skill.
Install one at a time with --skill:
Setup
The script-backed skills read your Mountaya API keys from the environment. Set them once so agents can authenticate.
MOUNTAYA_PUBLISHABLE_KEYpk_…
Your publishable key. Identifies your organization and is required for all products. Enable the scopes the skills need: data for the Data API, tiles for the Tile API, and embedding plus tiles for Map Embedding.
MOUNTAYA_SECRET_KEYsk_…
Your secret key. Used to create session tokens for the Data API. Keep it server-side only.
Create keys in your organization's API settings and enable the scopes each skill needs. The skills read these variables when set, and otherwise fall back to a pk_… placeholder you replace by hand.