# Use peaks.fyi data Public mountain research and forecasts. No account or API key is required. Connect your AI assistant with copyable setup instructions and example prompts: https://peaks.fyi/connect You can retrieve the data below with ordinary HTTP GET; no browser interaction is needed. ## Direct API and MCP Read the compact API instructions first, then call its documented search and data endpoints: https://peaks.fyi/api/agent?view=compact MCP clients can connect directly at: https://peaks.fyi/mcp ## Link-only browser fallback Compact directory, including alternative names and countries: https://peaks.fyi/directory Choose a mountain to find linked weather dates, altitudes, routes, seasons and hut contacts. These small text pages work without JavaScript. Every next page has a real URL; no API setup is needed. ## Start with the user's mountain or request Find a mountain by name or alias: https://peaks.fyi/api/agent/search?query=Almanzor The result supplies the canonical peak slug and timezone. Use that slug in subsequent requests; do not guess it from a mountain's name. Read a peak's routes, season, access and source information: https://peaks.fyi/api/agent/get_peak?slug=pico-almanzor§ions=%5B%22overview%22%2C%22routes%22%2C%22seasons%22%2C%22access%22%2C%22provenance%22%5D Read summit weather: https://peaks.fyi/api/agent/get_weather?slug=pico-almanzor&targetId=summit Add start and end as ISO 8601 timestamps with a timezone to request a time window. end is exclusive. Check the returned coverage, issue time, freshness, units and altitude. Precipitation uses accumulation intervals, not sums of point readings. Read hut contacts and booking information: https://peaks.fyi/api/agent/get_huts?slug=pico-almanzor Search for routes meeting constraints on the same route: https://peaks.fyi/api/agent/search_routes?query=Austria&maxDifficulty=3&maxRoundTripHours=6 For routes near a town, use the near coordinate/radius filter documented in the schema; route-name text search does not geocode towns. Use documented filters for difficulty, duration, glacier status and transport. A peak-level match does not establish that every route fits. ## Other tasks and complete schemas https://peaks.fyi/api/agent https://peaks.fyi/api/agent/openapi.json All documented tools accept GET query parameters or POST JSON. Numbers, booleans, arrays and objects use JSON values in the query. For nested inputs you may instead use a single input parameter containing a URL-encoded JSON object. Source links, unknowns and per-result errors are retained. For passages, use get_route_point after finding the route ID. For compact route comparisons use get_route_briefs. For operating notices use get_notices with the trip date. For exact sunrise and sunset use get_daylight with the date and timezone. Follow pagination when a complete result set matters. ## MCP clients https://peaks.fyi/mcp Public Streamable HTTP MCP, no authentication. Add this connection in a client that supports MCP. A website visit alone does not install a connection. Ordinary GET access above works without MCP setup. ## Interpretation Historical seasons are not daily forecasts. Unknown glacier or accessibility facts are not negative facts. A hut's capacity is not vacancy, and a published season is not confirmation for another year. We provide contacts and evidence, not reservations, payments, live equipment stock, guaranteed transport schedules, navigation certification or a safe-to-climb verdict. Cite source URLs and retain source dates and conflicts. If required evidence is unavailable, explain the gap and the next useful verification step.