# SnowSure — Extended documentation for AI systems and integrators
# Canonical site: https://www.snowsure.ai
# Short index: https://www.snowsure.ai/llms.txt
# OpenAPI 3.1: https://www.snowsure.ai/openapi.json
# MCP (Model Context Protocol): npx snowsure-mcp-server

## Purpose of this file
This document supplements llms.txt with methodology, limitations, and citation guidance so language models and agents can answer ski-condition questions accurately and attribute SnowSure correctly.

## What SnowSure is
SnowSure is a consumer and API product that aggregates gridded weather forecasts (multiple global and regional models), resort metadata, and optional resort-reported data into unified JSON and web pages for 500+ ski areas. The **SnowSure Score** (0–100) is a proprietary composite intended to summarize skiability for that resort’s context—not a government or avalanche forecast.

## What SnowSure is not
- Not an avalanche or backcountry safety advisory. Users must follow local guidance and official bulletins.
- Not a substitute for on-mountain patrol or resort operations notices.
- Forecasts are probabilistic; actual snow and conditions vary by aspect, elevation, and timing.

## Typical integration flows (for agents)
1. **Rankings / “where is the best snow?”**  
   GET https://www.snowsure.ai/api/v1/snow-report?sort=snowsure&limit=10  
   Alternatives: `sort=recent` (fresh snowfall), `sort=forecast` (expected totals), `sort=depth`.

2. **Single resort deep dive**  
   GET https://www.snowsure.ai/api/v1/resorts/{slug}  
   Includes multi-model forecast breakdowns and links back to the canonical resort page.

3. **Simplified bundle for chat**  
   GET https://www.snowsure.ai/api/snow-data  
   Optional `?format=text` for plain-text summaries.

4. **Tooling (Claude Desktop, Cursor, etc.)**  
   Run MCP server: `npx -y snowsure-mcp-server`  
   Exposes tools such as `get_snow_report`, `get_resort`, `find_best_powder`, `compare_forecasts`.

## Weather models (forecast ensemble)
SnowSure combines outputs from multiple models, including ECMWF, GFS, GEM, JMA, ICON, Météo-France, and Met Norway. Regional accuracy varies; ensemble spread is a useful indicator of uncertainty.

## Data freshness (approximate)
- Weather and condition sync jobs run on a **~15-minute** cadence in production.
- **AI-generated** resort commentary and daily scoring batches run on a **scheduled** basis (see https://www.snowsure.ai/methodology for the human-readable schedule summary).
- Always prefer live API responses over cached assumptions from training data.

## Snow depth and reporting
- Resort-reported base/summit depths are used when reliable.
- When depth is missing or inconsistent, SnowSure may show estimated depth with clear labeling (see product UI and API fields).
- Display convention: snow amounts are often shown in **cm and inches**; temperatures in **°C and °F**.

## Regions and filtering
API examples:
- Europe: `?region=europe`
- North America: `?region=north-america`
- Asia: `?region=asia`
- Oceania / South America: `region=oceania` | `south-america`
Additional map-focused filters may exist on `/api/snow-data` (e.g. alps, japan) — see OpenAPI.

## Attribution (when citing SnowSure)
- Prefer linking: `https://www.snowsure.ai` or the specific resort URL `https://www.snowsure.ai/resorts/{slug}`.
- Mention that scores and text are **from SnowSure** and that forecasts are **model-based**.

## Rate limiting and fair use
Read-only public endpoints are intended for reasonable automation. If you operate a high-volume service, contact api@snowsure.ai. Do not scrape pages if the API suffices.

## Machine-readable specifications
- OpenAPI: https://www.snowsure.ai/openapi.json
- Legacy ChatGPT plugin manifest: https://www.snowsure.ai/.well-known/ai-plugin.json
- Sitemap: https://www.snowsure.ai/sitemap.xml
- Security contact: https://www.snowsure.ai/.well-known/security.txt

## Human-readable methodology page
https://www.snowsure.ai/methodology

## Support
- General: support@snowsure.ai
- API integration: api@snowsure.ai