Niches · Weather & climate data

Answer for a named place in its local time

Two or three companies' docs show a full fit.

2companies, full fit
10companies, fit with a limit
33companies carry the tag
10share of the category's work
5first-hand accounts

What counts as done

The place resolves to the intended coordinates, with the resolved name in the requested language, and every timestamp in the response carries the location's UTC offset or time zone name.

How agents ask for it: weather in Springfield, forecast for my postcode, what time is sunset there

Does the job 2

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
meteoblue Weather API B
meteoblue AG
The location search API ranks results by importance and population, localises names by locale path (Bâle for Basel), and returns timezone; forecasts take tz or detect it and return utc_timeoffset. source
Xweather Weather API B
Vaisala Oyj
p accepts coordinates, place names, postcodes, airports and more, /places/search ranks matches, lang sets the output language, and responses carry tzname and dateTimeISO with the local offset. source

Does the job, with a limit 10

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)
Location search takes city names, postal codes, coordinates and points of interest and returns location keys with time zone information, but ranking of ambiguous matches was not shown in the pages read. source
Google Weather API (Maps Platform) BB
Google LLC or a regional Google entity, by billing country
Location is latitude and longitude only, so a named place needs Google's separate Geocoding API; responses carry the time zone and local display times, and languageCode localises text. source
Meteosource Weather MCP D
Meteosource
search_places turns a name, postcode or coordinates into a place_id, but whether it returns ranked candidates or names in a chosen language isn't stated. source
OpenWeather One Call API C
OpenWeather Ltd
One Call takes coordinates only; names need the separate Geocoding API, which acc-14 found often resolves the wrong place. timezone_offset is given but timestamps stay UTC. source
Pirate Weather B
PirateWeatherAPI (Ontario, Canada)
Accepts city,country as well as coordinates and returns nearestCity, nearestSubNational, timezone and offset, but no ranked candidates for an ambiguous name. source
Tomorrow.io Weather API D
The Tomorrow Companies Inc.
location accepts a place name and the response returns the resolved name and type; a timezone parameter can localise times. No ranked candidates, and acc-38 got UTC offsets of zero from Tomorrow.io. source
Visual Crossing Weather API B
Visual Crossing Corporation
Takes an address, partial address, postcode or coordinates and returns resolvedAddress with timezone and tzoffset, but no ranked candidates; lang translates conditions only and acc-34 got names in local script. source
The Weather Company Data APIs C
The Weather Company, LLC
Location Services resolve geocodes, postal keys, IP and IATA codes, and responses translate named fields by language with local times; contract-only access. source
WeatherAPI.com B
Zoomash Ltd
q takes a city, coordinates, postcode, IP and more, a search/autocomplete endpoint returns candidates, and the location object carries tz_id and localtime. lang translates condition text only, and acc-38 saw UTC offsets of zero via an integration. source
Weatherbit API D
Weatherbit LLC
Takes lat/lon, city with country, postal code or station, with a /geocode endpoint, and returns city_name and timezone; acc-38 found UTC offsets of zero via an integration. source

Doesn't do this job 4

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

ListingWhy
Met Office Weather DataHub (Site Specific) F
Met Office, an executive agency of the UK government
The official script takes latitude and longitude only; includeLocationName returns a name for the point but there is no place search. source
Meteomatics Weather API E
Meteomatics AG
Locations are coordinates, lines, polygons or country shortcuts; no place-name search was found, and times come back in UTC. source
NOAA National Weather Service API (api.weather.gov) D
National Weather Service, NOAA, U.S. Department of Commerce
No place-name or postcode search; the API takes coordinates, grid cells, stations or zones only. source
Stormglass API E
Storm Glass AB
Coordinates only, and the docs say every timestamp sent and received is UTC; local time is left to the caller. source

What stops agents finishing

  • ambiguous names resolved without asking
  • times returned in UTC with no offset

Around it

Before: chat.user-names-place. After: weather.forecast, weather.current.

Where this comes from

Weight 10 of 100 in Weather & climate data: 5 of 43 accounts: wrong places from name search, names in local script, crag points offset, UTC-only times in three APIs

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