{
  "data": null,
  "kind": "anchor.page",
  "links": {
    "api": "https://www.anchorterminal.com/api/v1/index.json",
    "html": "https://www.anchorterminal.com/niches/weather.history/",
    "json": "https://www.anchorterminal.com/niches/weather.history/index.json",
    "llms": "https://www.anchorterminal.com/llms.txt",
    "markdown": "https://www.anchorterminal.com/niches/weather.history/index.md",
    "mcp": "https://www.anchorterminal.com/mcp",
    "slim": "https://www.anchorterminal.com/niches/weather.history/index.min.md"
  },
  "markdown": "No company's docs show a full fit yet. The listings below do the job with a limit, or not at all.\n\n| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |\n| --- | --- | --- | --- | --- |\n| 0 | 12 | 13 | 14 | 5 |\n\n## What counts as done\n\nDaily 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.\n\nHow 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\n\n## Does the job, with a limit\n\nIt 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.\n\n- **meteoblue Weather API (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.\n- **Meteomatics Weather API (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).\n- **Meteosource Weather MCP (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.\n- **OpenWeather One Call API (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).\n- **Pirate Weather (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.\n- **Stormglass API (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.\n- **Tomorrow.io Weather API (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.\n- **Visual Crossing Weather API (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.\n- **The Weather Company Data APIs (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.\n- **WeatherAPI.com (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.\n- **Weatherbit API (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.\n- **Xweather Weather API (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.\n\n## Couldn't check\n\nThe docs were closed to us, or silent. These carry no mark either way.\n\n- **Met Office Weather DataHub (Site Specific) (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.\n\n- not this job: AccuWeather Core Weather API + MCP (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.\n- not this job: Google Weather API (Maps Platform) (Google LLC or a regional Google entity, by billing country): history.hours returns only the last 24 hours; nothing older is offered.\n- not this job: NOAA National Weather Service API (api.weather.gov) (National Weather Service, NOAA, U.S. Department of Commerce): Only seven days of station observations are retained; the docs send archive requests to NCEI.\n\n## What stops agents finishing\n\n- history only 24 hours back (Google)\n- history on a higher plan with its own quota (Weatherbit, meteoblue)\n- per-data-point billing makes a backfill or a scraper expensive\n- range caps per call (Stormglass 10 days, Tomorrow.io 31)\n\n## Around it\n\nBefore: weather.resolve-place. After: spreadsheets.append-rows, data.analyse.\n\n## Where this comes from\n\nWeight 14 of 100 in Weather \u0026 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\n\nAs data: https://www.anchorterminal.com/api/v1/use-cases/weather.history.json, or the MCP tool get_use_case with id weather.history. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.\n",
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "attributionRequired": true,
    "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-11-16",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.8",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run",
    "terms": "https://www.anchorterminal.com/terms/#data"
  },
  "page": {
    "breadcrumbs": [
      {
        "name": "Home",
        "url": "https://www.anchorterminal.com/"
      },
      {
        "name": "For agents",
        "url": "https://www.anchorterminal.com/agents/"
      },
      {
        "name": "Niches",
        "url": "https://www.anchorterminal.com/niches/"
      },
      {
        "name": "Look up past weather for a date range or baseline",
        "url": ""
      }
    ],
    "description": "Look up past weather for a date range or baseline: 0 companies fully do it, 12 with a limit, 13 carry the tag. Every listing in Weather \u0026 climate data with the reason and a source.",
    "facts": null,
    "h1": "Look up past weather for a date range or baseline",
    "image": "https://www.anchorterminal.com/assets/og/default.png",
    "path": "/niches/weather.history/",
    "published": "",
    "section": "agents",
    "title": "Look up past weather for a date range or baseline | Anchor Terminal",
    "toc": null,
    "updated": "2026-11-15",
    "url": "https://www.anchorterminal.com/niches/weather.history/"
  },
  "tokens": {
    "markdown": 1500,
    "slim": 380
  },
  "version": 1
}
