Niches · Weather & climate data

Get the forecast for a place over the next hours or days

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
16companies, fit with a limit
17companies carry the tag
30share of the category's work
24first-hand accounts

What counts as done

Hourly or daily values (temperature, precipitation amount and probability, wind, condition) for every step in the window in one call, with units stated and timestamps carrying the location's offset; the response says when the forecast was issued.

How agents ask for it: what is the weather this weekend, will it rain tomorrow afternoon, give me the 10-day forecast for Lisbon, hourly forecast for the race

Does the job, with a limit 16

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
AccuWeather Core Weather API + MCP D
AccuWeather Intl., LLC (API terms), AccuWeather, Inc. (privacy)
Hourly forecasts run to 120 hours and daily to 15 days with precipitation probability, wind and phrases, but each place first needs a location-key lookup, forecasts default to imperial, and the free tier was withdrawn with old keys invalidated (acc-19, acc-20); new access is a 14-day trial. source
Google Weather API (Maps Platform) BB
Google LLC or a regional Google entity, by billing country
forecast.hours returns up to 240 hours with precipitation probability and amount, wind, condition, unitsSystem and timeZone plus local displayDateTime, but pages hold at most 24 hours each, so a ten-day window takes ten billable calls. Japan and South Korea stop at 72 hours. source
Met Office Weather DataHub (Site Specific) F
Met Office, an executive agency of the UK government
The official script calls /point/{timesteps} with hourly, three-hourly or daily steps by latitude and longitude, key in a header. The DataHub docs are behind sign-in, and acc-25 found daily and twice-daily forecasts with precipitation null. source
meteoblue Weather API B
meteoblue AG
Packages such as basic-1h,basic-day combine in one call with forecastDays, tz, unit parameters and modelrun_utc and modelrun_updatetime_utc in metadata; the basic package is seven days. Each call costs thousands of credits from a 10-million free year, and acc-41 found forecast points offset from crag coordinates. source
Meteomatics Weather API E
Meteomatics AG
One REST call takes an ISO time range with step, any list of parameters with units in the name (t_2m:C) and a point, line or polygon; responses are in UTC. Access is by contract only, with credentials sent after a sales conversation, and acc-33 hit undocumented call limits. source
Meteosource Weather MCP D
Meteosource
get_forecast returns current, hourly (168 h) and daily (30 days) data with warnings for up to 20 places in one call, a variables filter and local-convention units; the README states neither the timestamp offset nor an issue time. source
NOAA National Weather Service API (api.weather.gov) D
National Weather Service, NOAA, U.S. Department of Commerce
/points then /forecast/hourly gives seven days of hourly periods, and gridData adds precipitation amount and probability, gusts and uom units with updateTime. Two calls per place, US only, and seven days rather than fifteen; acc-08 and acc-10 use it. source
OpenWeather One Call API C
OpenWeather Ltd
One call returns 48 hours hourly and 8 days daily with pop, rain, wind, gusts and units, plus timezone and timezone_offset, but times are Unix UTC, there is no issue time, and the subscription needs a card (acc-01); 3.0 and 4.0 clash on one account (acc-21). source
Pirate Weather B
PirateWeatherAPI (Ontario, Canada)
One call gives hourly (48 h, 168 with extend=hourly) and daily blocks with precipProbability, intensity, accumulation, gusts, units, timezone and offset, and sourceTimes says when each model last ran. Accounts report a key revoked without notice (acc-27) and sign-up giving no key (acc-32). source
Stormglass API E
Storm Glass AB
/v2/weather/point returns hourly values per source for the params asked (precipitation, gust, wind, temperature) between start and end, but timestamps are UTC only, there is no precipitation probability or condition text, and the free plan is 10 requests a day. source
Tomorrow.io Weather API D
The Tomorrow Companies Inc.
/weather/forecast returns 1h and 1d steps with precipitationProbability, rainAccumulation, windGust, temperatureApparent and a units switch, but the free plan reaches only five days ahead, times come back in UTC, and no issue time was found. acc-23 saw polling go stale. source
Visual Crossing Weather API B
Visual Crossing Corporation
One Timeline call returns 15 days of daily and hourly values (precipprob, precip, wind, conditions) with unitGroup, timezone and tzoffset, and works without a key. No issued or model-run time is in the documented response. source
The Weather Company Data APIs C
The Weather Company, LLC
Daily forecasts carry precipChance, qpf, local day and night parts and expirationTimeUtc, but 3, 5, 7, 10 and 15 days are separate endpoints each authorised separately (401 otherwise), and access is by contract with a trial for enterprise customers. source
WeatherAPI.com B
Zoomash Ltd
forecast.json returns daily and hourly values (chance_of_rain, totalprecip, gust, feelslike in both unit systems) with tz_id, localtime and time_epoch, but only three days on Free and 14 on higher plans, and no issue time. acc-37 could not reach the key page. source
Weatherbit API D
Weatherbit LLC
/forecast/daily returns up to 16 days and /forecast/hourly hourly steps with pop, precip, wind_gust_spd, app_temp and timestamp_local plus timezone, but daily periods run 00:00 to 23:59 UTC rather than local days, no issue time is given, and hourly and daily are separate calls. source
Xweather Weather API B
Vaisala Oyj
/forecasts returns daily or hourly intervals with pop, precipitation, feelslike and gusts in both unit systems, dateTimeISO with offset and tzname, and fields and lang parameters. No issue time was found in the specification, and one request can cost several accesses. source

What stops agents finishing

  • free tier withdrawn or keys invalidated (AccuWeather 2025)
  • sign-up needs a card or a person, or the key page fails
  • each forecast length is a separate entitlement (Weather Company)
  • a forecast field is null for the step asked

Around it

Before: weather.resolve-place, maps.geocode, scheduling.find-slot. After: messaging.send, travel.plan-trip, scheduling.create-event.

Where this comes from

Weight 30 of 100 in Weather & climate data: 24 of 43 accounts, the most common job: home dashboards, Home Assistant, bots and apps on HN and GitHub

The same as data: /api/v1/use-cases/weather.forecast.json, or the MCP tool get_use_case with id weather.forecast. 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.