Niches · Weather & climate data

Look up past weather for a date range or baseline

No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.

0companies, full fit
12companies, fit with a limit
13companies carry the tag
14share of the category's work
5first-hand accounts

What counts as done

Daily or hourly observed or reanalysis values for every day in the range, with the source named, within the range limit of one or a few calls; the earliest available date is documented.

How agents ask for it: what was the weather on 3 March, how much did it rain last month, compare this summer with the last 20 years, yesterday's temperature

Does the job, with a limit 12

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
meteoblue Weather API B
meteoblue AG
The Forecast API returns up to 4 past days with history_days; long series sit in the separate History API, which needs a paid plan per the listing and whose earliest date was not read. source
Meteomatics Weather API E
Meteomatics AG
The Weather API page index states historical data from 1940 through the same time-range query; access is contract-only and per-call limits are undocumented (acc-33). source
Meteosource Weather MCP D
Meteosource
get_weather_history gives hourly (14 days per call), daily or monthly (366 days per call) history with normals over 20 years, but the plan sets how far back the archive reaches and older days need an add-on; the data source is not named. source
OpenWeather One Call API C
OpenWeather Ltd
Timemachine covers any timestamp from 1 January 1979 and day_summary gives daily aggregates, but each is one call per timestamp or day, so a range costs many calls (acc-03). source
Pirate Weather B
PirateWeatherAPI (Ontario, Canada)
Time Machine takes a time per request and uses ERA5 reanalysis (URMA for the last 10 days in North America), so the source is named, but it is one request per point in time and the earliest date is not stated on the pages read. source
Stormglass API E
Storm Glass AB
Historical point data runs from 2014 on ERA5, named in the docs, but each response covers at most 10 days and the newest week is usually missing. source
Tomorrow.io Weather API D
The Tomorrow Companies Inc.
Free plans reach back 24 hours (premium 7 days); the deeper archive is metered in tokens with X-Tokens-Cost headers and no public price, and ranges are split per call. source
Visual Crossing Weather API B
Visual Crossing Corporation
A date range in one call returns daily or hourly history with source obs or remote, but the earliest date is given only as '50+ years' in marketing text, and billing per record made a scraper costly in acc-04. source
The Weather Company Data APIs C
The Weather Company, LLC
The History on Demand package has synchronous historical queries by grid point with usage-saving utilities, but it is a separate contract package and the earliest date was not read. source
WeatherAPI.com B
Zoomash Ltd
history.json covers any date since 1 January 2010, but only one day back on Free, seven on Starter, 365 on Pro+ and the full archive on Business. source
Weatherbit API D
Weatherbit LLC
/history/daily, hourly and subhourly take start_date and end_date and return sources and station_id, but the earliest date and per-call range are not in the specification, and history needs a paid plan per the listing. source
Xweather Weather API B
Vaisala Oyj
/observations/archive gives daily historical observations back to 2011 with limit and skip paging; the deeper conditions or model archive and plan limits were not read. source

Couldn't check 1

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
Met Office Weather DataHub (Site Specific) F
Met Office, an executive agency of the UK government
No history parameter in the official script, and the DataHub docs that would say whether past data is offered are behind sign-in.

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
AccuWeather Core Weather API + MCP D
AccuWeather Intl., LLC (API terms), AccuWeather, Inc. (privacy)
Only the past 6 or 24 hours of current conditions are offered; there is no historical archive. source
Google Weather API (Maps Platform) BB
Google LLC or a regional Google entity, by billing country
history.hours returns only the last 24 hours; nothing older is offered. source
NOAA National Weather Service API (api.weather.gov) D
National Weather Service, NOAA, U.S. Department of Commerce
Only seven days of station observations are retained; the docs send archive requests to NCEI. source

What stops agents finishing

  • history only 24 hours back (Google)
  • history on a higher plan with its own quota (Weatherbit, meteoblue)
  • per-data-point billing makes a backfill or a scraper expensive
  • range caps per call (Stormglass 10 days, Tomorrow.io 31)

Around it

Before: weather.resolve-place. After: spreadsheets.append-rows, data.analyse.

Where this comes from

Weight 14 of 100 in Weather & climate data: 5 of 43 accounts (yesterday's weather sites, Dark Sky Time Machine replacement, White Christmas baseline, thermostat analysis); buyer check names history depth

The same as data: /api/v1/use-cases/weather.history.json, or the MCP tool get_use_case with id weather.history. Other jobs in this category: /api/v1/niches?category=weather.

Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.