Publish or consume a ski-lift open/closed status feed using the de-facto JSON patterns established by Liftie and OnTheSnow
domain: liftie.info · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Note there is no single industry-wide standard for lift-status JSON; Liftie and OnTheSnow each define their own resort/lift schema
For a resort with its own JSON status feed, mirror Liftie's minimal descriptor pattern: an 'api' block with host + pathname, resolved via HTTP GET
Model each lift as {name, status} at minimum (Liftie), or the richer {name, type, status enum} used by OnTheSnow's lifts.details array
If no native feed exists, follow Liftie's fallback pattern: scrape the resort's public lift-status HTML page with a CSS-selector-based parser instead of assuming a JSON API
Cache aggressively - Liftie caches per-resort status server-side (once per minute) rather than hitting resort pages per browser request
Known gotchas
Because there's no ratified standard, expect to write a resort-specific adapter/parser rather than a single universal client
Lift status 'closed' can mean seasonal closure, weather hold, or scheduled maintenance - the same status value can mean different things per resort unless you also check textual notes
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?