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
Agentic Resource Discovery manifest — MCP servers, APIs, and snow data bundle
Concise site summary for LLM crawlers
Extended context — pages, FAQs, intelligence contract
MCP server for Snowdata corporate content
ARD discovery cards with full tool schemas — live + content
Discovery JSON for both content and live-snow MCPs
Legacy OpenAI plugin-style discovery
OpenAPI 3.1 for public intelligence and Answer Engine proxies
POST /search for snow-specific agent resource discovery
Data provenance, verification methodology, ARD trustManifest
All public pages
Crawler rules + AI bot allowlist
Content MCP
Connect agents researching Snowdata as a company — onboarding, pricing, pages, FAQs. Endpoint:
https://www.snowdata.ai/api/mcpTools 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"
}
}
}Publish your own ski resource
Run a ski or snow MCP server, API, or agent? Publish a signed ai-catalog.json and join the SnowData Network — verified, and discoverable to every AI agent that asks a ski question.
Join the SnowData Network →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.