llms.txt
Compare with other sites' llms.txt files →# Snotel
> Public SNOTEL snow observations from NRCS, exactly as reported, plus the NWS weather around each station and a registry of North American ski resorts, served by a read-only REST API and an MCP server. Snotel is an independent project with closed-source code, not affiliated with or operated by NRCS or NOAA. Credit data from it as "Data: USDA NRCS, NOAA/NWS via Open Snotel" (resort data: "OpenSkiData contributors, ODbL").
Every link below is the Markdown of one docs page. Fetch only the pages a task needs.
- REST API: https://opensnotel.com/api/v1 (public, read-only, no key)
- OpenAPI 3.1: https://opensnotel.com/api/v1/openapi.json
- MCP server: https://opensnotel.com/mcp (Streamable HTTP, no key); an MCP client should use it instead of these pages
- Giving Snotel to an agent, and the rules that keep its answers right: https://opensnotel.com/docs/agents.md
- Every page as one file, only when you need all of them: https://opensnotel.com/llms-full.txt
Stored observations are observed values only: derived, inferred and forecast values are labeled as such, a missing reading is null and never zero, and a change in snow depth is not snowfall.
## Start
- [Overview](https://opensnotel.com/docs.md): Start here: what Snotel is, what data it serves (SNOTEL observations, NWS weather context, a ski resort registry), how to reach it over REST or MCP, and which page answers which task.
- [Quickstart](https://opensnotel.com/docs/quickstart.md): Make a first request: the latest snow water equivalent and snow depth at a station with curl, the stations near a coordinate, a range of history, and connecting an MCP client.
- [Agents](https://opensnotel.com/docs/agents.md): What to give an agent so it works with Snotel accurately: the MCP server, /llms.txt or one page's Markdown, plus the rules that keep it from plausible but wrong snow answers.
- [Data model](https://opensnotel.com/docs/data-model.md): The fields every Snotel value carries and what each means: station, triplet, element, observation, interval, unit, flags, freshness, revision and provenance. Read before storing Snotel data.
## API
- [Overview](https://opensnotel.com/docs/api.md): Use the REST API at /api/v1: every endpoint, the conventions all responses follow (UTC times, null for missing, the source's units and flags), request bounds and caching.
- [Stations](https://opensnotel.com/docs/api/stations.md): List or search stations by name, state or network, and get one station by its triplet: location, elevation, UTC offset, period of record and the measurements it reports.
- [Observations](https://opensnotel.com/docs/api/observations.md): Get the latest reading of each sensor with a freshness verdict, or daily or hourly readings over a date range, with units, quality flags, original values and revisions.
- [Nearest stations](https://opensnotel.com/docs/api/nearest.md): Find the SNOTEL stations nearest a latitude and longitude, ranked by great-circle distance, with limit, radius, network and active filters.
- [Snowpack Context](https://opensnotel.com/docs/api/snowpack.md): Compare a station's snowpack with its own WY1991–2020 history: 24 h and 72 h change, percent of median, percentile and rank, a water year against its band, and stations ranked by gain or anomaly.
- [Weather](https://opensnotel.com/docs/api/weather.md): Get the weather around a SNOTEL station: the newest NWS forecast for its grid cell, nearby NWS observations and active alerts, each labeled observed or forecast and where it was measured.
- [Resorts](https://opensnotel.com/docs/api/resorts.md): Look up North American ski resorts by country, region, status or name, get one by slug with its operating area and provenance, or download the whole registry as CSV, JSON or GeoJSON.
- [Errors](https://opensnotel.com/docs/api/errors.md): Handle API errors: the one error shape every endpoint returns, each code with its HTTP status, and what to do about it.
## MCP
- [Overview](https://opensnotel.com/docs/mcp.md): What the MCP server at /mcp gives an agent: nine read-only tools over the same data as the REST API, and what it deliberately does not expose.
- [Connect](https://opensnotel.com/docs/mcp/connect.md): Connect an MCP client to https://opensnotel.com/mcp: the URL, the Streamable HTTP transport, a Claude Code command, a JSON config, and how to check the connection.
- [Tools](https://opensnotel.com/docs/mcp/tools.md): The nine MCP tools: finding stations, their readings and history, Snowpack Context (station_context, station_climatology, snow_rankings) and station weather; arguments, limits, results, freshness and errors.
- [Examples](https://opensnotel.com/docs/mcp/examples.md): Worked agent tasks over MCP: latest snow depth near a point, a week at three stations, the largest gains in snow water equivalent, how unusual today is, a water year against history, and freshness.
## Data
- [Measurements](https://opensnotel.com/docs/data/measurements.md): What snow water equivalent (SWE), snow depth, precipitation and air temperature are, their element codes and units, how daily and hourly differ, and why null is never zero.
- [Quality](https://opensnotel.com/docs/data/quality.md): Interpret the source's quality flags (V, E, K, M) and review flags (P, A, R), isProvisional, original values the source edited or blanked, and what a flag does not guarantee.
- [Freshness](https://opensnotel.com/docs/data/freshness.md): How recent is this value? Which timestamp is the actual observation time, how often Snotel reads NRCS, when a reading counts as stale, and why a zero can still be fresh.
- [Provenance](https://opensnotel.com/docs/data/provenance.md): Which values are observed, derived, inferred or forecast, what to credit when you show Snotel data to users, and why a rise in snow depth is not snowfall.
- [Resort registry](https://opensnotel.com/docs/data/resorts.md): Where the ski resort registry comes from, how a resort keeps a stable id and slug, which of its fields are derived, and the ODbL license and attribution to show.
## Reference
- [Station IDs](https://opensnotel.com/docs/reference/station-ids.md): The identifier to store for a station: the NRCS triplet such as 312:ID:SNTL, its format, why the station number alone isn't unique, and a parser.
- [Time and dates](https://opensnotel.com/docs/reference/time.md): How timestamps work: observedAt in UTC, localDate at the station's fixed offset with no daylight saving, daily vs hourly periods, and the water year that starts October 1.
- [OpenAPI](https://opensnotel.com/docs/reference/openapi.md): Where the machine-readable OpenAPI 3.1 document for /api/v1 lives, what it covers, and how to generate a typed client from it.