Retrieve a combined historical-observation-plus-forecast weather timeline for a location and date range using Visual Crossing's Timeline Weather API
domain: weather.visualcrossing.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Issue a GET request to the Timeline Weather API with location and a date range spanning past, present, and/or future dates in one call.
Let the API automatically blend historical observations, the current multi-day forecast, and long-term statistical forecast data depending on which portion of the range is requested.
For point-in-time 'what was forecast on day X for day Y' analysis, use the separate Historical Forecast API's byrun mode instead, which exposes rundatetime and forecastday fields.
Select the desired granularity (days, hours, or current conditions) via the include parameter.
Choose a unit group (us/metric/uk) explicitly in the request to avoid ambiguity in returned values.
Known gotchas
The standard Timeline API returns the 'best known' data per date (observed if past, forecast if future) — it does NOT show what an older forecast run predicted; that requires the separate Historical Forecast API.
Very long date ranges combined with hourly include values can consume a large number of billed records per call under Visual Crossing's cost model.
Historical Forecast (byrun) data availability only extends back to when Visual Crossing began archiving forecast runs, not the full historical-observation depth.
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?