# Report current conditions at a place

> Report current conditions at a place: 4 companies fully do it, 10 with a limit, 15 carry the tag. Every listing in Weather & climate data with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/weather.current/
- Markdown: https://www.anchorterminal.com/niches/weather.current/index.md (~1,600 tokens)
- Slim: https://www.anchorterminal.com/niches/weather.current/index.min.md (~430 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/weather.current/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

Four or more companies' docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 4 | 10 | 15 | 18 | 9 |

## What counts as done

Temperature, feels-like, precipitation, wind and condition for the point with an observation or analysis time, in one call; the response says whether the value is a station observation or a model analysis.

How agents ask for it: what is the weather now; is it raining in Manchester; current temperature at home; how windy is it right now

## Does the job

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

- **Pirate Weather (PirateWeatherAPI (Ontario, Canada))**: The currently block has temperature, apparentTemperature, precipitation, wind and summary with a time, and flags name the sources; in North America it comes from the RTMA-RU analysis, refreshed every 15 minutes.
- **Visual Crossing Weather API (Visual Crossing Corporation)**: currentConditions returns temp, feelslike, precip, wind and conditions with datetimeEpoch, and each object's source field says obs, fcst or statistical, with the stations used.
- **Weatherbit API (Weatherbit LLC)**: /current returns temp, app_temp, precip, wind, gust and weather with ob_time, station and sources, so the agent can see it is an observation and from where.
- **Xweather Weather API (Vaisala Oyj)**: /conditions returns current temperature, feels-like, precipitation, wind and weather for a point as model conditions, while /observations returns station reports; the two are separate endpoints, so the source type is explicit.

## Does the job, with a limit

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.

- **AccuWeather Core Weather API + MCP (AccuWeather Intl., LLC (API terms), AccuWeather, Inc. (privacy))**: Current conditions are described as real-time observations with RealFeel, precipitation, wind and description, in both unit systems, but need the location key first; acc-39 saw the precipitation endpoint fail in China.
- **Google Weather API (Maps Platform) (Google LLC or a regional Google entity, by billing country)**: currentConditions returns temperature, feels-like, precipitation, wind and condition with currentTime and timeZone, but does not say whether values are station observations or model analysis.
- **meteoblue Weather API (meteoblue AG)**: A /packages/current endpoint exists, but per the listing current conditions need a paid plan, and whether it marks observation versus mLM analysis was not established.
- **Meteomatics Weather API (Meteomatics AG)**: Any parameter can be queried for now, and station parameters exist beside model output, but nothing read says which a default value is, and access needs a contract.
- **Meteosource Weather MCP (Meteosource)**: Current conditions come inside get_forecast, but the README does not say whether they are station observations or model analysis.
- **NOAA National Weather Service API (api.weather.gov) (National Weather Service, NOAA, U.S. Department of Commerce)**: /stations/{id}/observations/latest returns a station observation with its time, so the source is explicit, but the agent must first find the station via /points, values stay null until QC, and they may lag 20 minutes.
- **OpenWeather One Call API (OpenWeather Ltd)**: current gives temp, feels_like, rain, wind, gusts and condition with dt, but does not say whether a value is a station observation or a model analysis, and acc-22 saw another place's data via an integration.
- **Tomorrow.io Weather API (The Tomorrow Companies Inc.)**: A realtime endpoint is listed and the data layers table gives a current step on every plan with temperatureApparent, precipitation and wind, but nothing read says whether values are observations or model analysis.
- **The Weather Company Data APIs (The Weather Company, LLC)**: Currents On Demand assimilates surface observations, radar, satellite, lightning and short-term models at request time, so values are labelled as a blended analysis; access is by contract only.
- **WeatherAPI.com (Zoomash Ltd)**: current.json gives temperature, feelslike, precipitation, wind and condition with last_updated, but doesn't say whether a value is a station observation or model output.

## Couldn't check

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

- **Met Office Weather DataHub (Site Specific) (Met Office, an executive agency of the UK government)**: Site Specific is a point-forecast product; whether any current or observation values come back could not be read, since the DataHub host redirects robots.txt and docs to sign-in.

- not this job: Stormglass API (Storm Glass AB): No current-conditions endpoint; the agent reads the present hour from the forecast, which has no feels-like or condition and doesn't distinguish observation from model.

## What stops agents finishing

- place search returns the wrong location
- one call per place for a location key before the data call (AccuWeather)
- current conditions only on a paid plan (meteoblue)

## Around it

Before: weather.resolve-place. After: messaging.send, notifications.push.

## Where this comes from

Weight 18 of 100 in Weather & climate data: 9 of 43 accounts (IRC bot, MCP tool, dashboards, Home Assistant, Breezy Weather)

As data: https://www.anchorterminal.com/api/v1/use-cases/weather.current.json, or the MCP tool get_use_case with id weather.current. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
