Get started
Get started

Create an account and keys

Create an account and keys

1

Sign up

Create your account at app.mountaya.com/registration.

2

Create an organization

The wizard asks How will your organization start? Pick the path that matches what you are building.

ChooseYou getYou need
Data API and MCP serverThe Data API and the MCP server, billed per requestA card. Nothing is charged until you call them.
Product accessMap Studio, Map Publishing, Embedded Studio, the Tile API, white labelAn agreement with our team. No card.

Not sure? Start with the Data API: an agreement can be added later. See pricing.

3

Create your keys

Open Organization → API keys (direct link). Organization owners and admins see this page.

  1. Create publishable key. Name it, then pick only the scopes this key needs.
  2. Create secret key. Copy it at once: it is shown only once.

Keep both out of your code:

export MOUNTAYA_PUBLISHABLE_KEY="pk_your_publishable_key"
export MOUNTAYA_SECRET_KEY="sk_your_secret_key"

Which key goes where

CredentialLooks likeLivesDoes
Publishable keypk_…Browser, app, or serverIdentifies your organization on every request
Secret keysk_…Your server onlyMints session tokens
Session tokensess_…Minted by your server, five minutesTravels beside the publishable key

Scopes

A publishable key opens only the APIs its scopes name.

ScopeConsole labelOpensAvailable
dataData APIRouting, places, and terrain queriesSelf-serve
mcpMCPThe MCP server for AI clientsSelf-serve
tilesTile APIBase maps and overlaysAgreement
publishingMap PublishingThe hosted embed and published contentAgreement
studio-embeddedEmbedded StudioThe editor in your product, and Map Studio API writesAgreement
managementManagement APIKeys, billing, members, settings, and webhooksAlone on its key

Notification emails

Mountaya emails members about some changes in their organization. Each member turns the optional ones off for each organization, under Organization → Notifications.

EmailSent toCan be turned off
InvitationThe address invitedNo
Role changedThe member, when someone else changed itNo: a security email
Removed from the organizationThe member, when someone else removed themNo: a security email
Collection deletedEvery member but the one who deleted itYes
Webhook endpoint failingOwners and adminsYes
Webhook endpoint disabledOwners and admins, but the one who disabled itYes

Every email is on until you turn it off. Security emails are always sent.

Next steps

Last updated