NWS Point Resolver API: Latitude and longitude in, NWS forecast grid, zone, county, timezone

Latitude and longitude in, NWS forecast grid, zone, county, timezone and the forecast/observation URLs out. The resolution step every weather call needs. Free.

Free — no key, no signup, rate-limited to 60 calls per minute per client.

How do you call it?

GET /v1/weather/point — product id weather_point. Over MCP, call answerpool_get with product_id=weather_point.

curl "https://answerpool.io/v1/weather/point?latitude=38.8894&longitude=-77.0352"

Live call: https://answerpool.io/v1/weather/point?latitude=38.8894&longitude=-77.0352 · JSON sample: /v1/samples/weather_point

What does the answer look like?

A representative response, the same static sample served at /v1/samples/weather_point.

{
 "as_of": "2026-09-03T16:00:00Z",
 "latitude": 38.8894,
 "longitude": -77.0352,
 "grid_id": "LWX",
 "grid_x": 97,
 "grid_y": 71,
 "city": "Washington",
 "state": "DC",
 "timezone": "America/New_York",
 "forecast_url": "https://api.weather.gov/gridpoints/LWX/97,71/forecast",
 "hourly_forecast_url": "https://api.weather.gov/gridpoints/LWX/97,71/forecast/hourly",
 "observation_stations_url": "https://api.weather.gov/gridpoints/LWX/97,71/stations",
 "forecast_zone": "https://api.weather.gov/zones/forecast/DCZ001",
 "county": "https://api.weather.gov/zones/county/DCC001",
 "note": "NWS keys forecasts by office grid, not by coordinates; this is the resolution step every other weather call needs first.",
 "source": "NOAA National Weather Service (api.weather.gov)",
 "refresh_after": "2026-09-17T11:15:00.000Z"
}

How fresh is it, and where does the data come from?

The fastest source behind this answer can change every 15 minutes, so every response carries a refresh_after timestamp — right now it would be 2026-09-17T11:15:00.000Z. Schedule the next call on that value rather than on a guess.

• NOAA National Weather Service (US federal public domain) — upstream: https://api.weather.gov

Method version 0.1.0 · serving cache 1 day · every response carries a result_id you can resolve at /v1/provenance.

When should you use it?

You have coordinates and need NWS identifiers or the city/timezone for them.

What you skip building

• two-step NWS grid lookup
• guessing forecast office codes

When should you not use it?

The forecast itself — /v1/weather/forecast does both steps in one call.

Where else can you find this?

• Catalog entry (JSON, free)
• OpenAPI schema — input and output types, prices, the 402 flow
• llms.txt — every product in one plain-text document