Pull NWS gridpoint forecast data to drive propane delivery-scheduling temperature inputs

domain: api.weather.gov · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Send a GET request to the points endpoint with the delivery location's latitude/longitude.
  2. Read the forecastGridData (or forecast/forecastHourly) URL from the response's properties.
  3. Send a GET request to that returned gridpoint URL to retrieve the raw forecast data.
  4. Parse the temperature time-series layer from the JSON response for the forecast window you need.
  5. Set a descriptive User-Agent header on every request, as required by the API.
  6. Cache responses locally and avoid re-polling the same gridpoint more than once per forecast cycle.

Known gotchas

Related routes

Use NOAA CPC's 7-day degree-day forecast (NDFD-based) to project near-term propane demand for a delivery zone
cpc.ncep.noaa.gov · 5 steps · unrated
Retrieve raw numerical forecast grid data (not just narrative forecasts) for a location from the NWS /gridpoints endpoint
api.weather.gov · 5 steps · unrated
Fetch NOAA CPC's population-weighted heating degree day statistics to calibrate a propane customer's delivery K-factor
cpc.ncep.noaa.gov · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans