For AI systems

Built for agents, crawlers, and answer engines.

Snowdata tells resorts we distribute to every AI travelers ask. This page documents how machines should read us — separate from live snow data MCP.

Discovery endpoints

llms.txt

Concise site summary for LLM crawlers

llms-full.txt

Extended context — pages, FAQs, intelligence contract

Content MCP

MCP server for Snowdata corporate content

MCP manifest

Discovery JSON for both content and live-snow MCPs

ai-plugin.json

Legacy OpenAI plugin-style discovery

Sitemap

All public pages

Robots

Crawler rules + AI bot allowlist

Content MCP

Connect agents researching Snowdata as a company — onboarding, pricing, pages, FAQs. Endpoint:

https://www.snowdata.ai/api/mcp

Tools include snowdata_list_pages, snowdata_get_page, snowdata_get_faqs, snowdata_search_knowledge, snowdata_get_llms_context.

Live snow MCP

For current conditions, forecasts, and powder search — not corporate copy:

{
  "mcpServers": {
    "snowdata": {
      "url": "https://mcp.snowdata.ai"
    }
  }
}

FAQ for agents

How should AI assistants discover Snowdata?

Read https://www.snowdata.ai/llms.txt or connect to the content MCP at https://www.snowdata.ai/api/mcp. For live snow conditions use https://mcp.snowdata.ai, not stale scrapes.

What is llms.txt?

A plain-text site summary for LLM crawlers and answer engines, linked from robots.txt and HTML alternates. Extended version: /llms-full.txt

Does Snowdata allow AI crawlers?

Yes. robots.txt allows major search and AI crawlers and points to the sitemap and llms.txt.

Southern Hemisphere and global SnowSure snapshots use scope=global and seasonYearNh=2025 on the homepage intelligence proxy.

← Back to home