# US Current Weather Observations API - NWS Station Temperature (`neverempty/us-weather-observations`) Actor

Current conditions and temperature from NOAA / US National Weather Service stations. Give a station id or a lat,lon point and it finds the nearest station. Sensors go missing all the time - this Actor leaves those fields null and says how many were actually measured, never zero.

- **URL**: https://apify.com/neverempty/us-weather-observations.md
- **Developed by:** [NeverEmpty](https://apify.com/neverempty) (community)
- **Categories:** Developer tools, News, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$5.00 / 1,000 observations

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## US Current Weather Observations API - NWS Station Temperature

Current conditions from **US National Weather Service** stations, straight from `api.weather.gov`. No scraping, no HTML parsing, no browser.

Give it a station id, or a point on the map and it finds the nearest reporting station for you.

### The thing this Actor does differently

**Weather sensors go missing.** A station reports temperature but not visibility. Another has no gust reading. This is normal and it happens constantly.

Most pipelines paper over it. Fill a missing wind gust with `0` and your dashboard now says "no gusts" when the truth is "nobody measured". Fill a missing temperature with `0` and you have just invented a freezing day.

This Actor **leaves missing readings as `null`**, and tells you how many of the nine core measurements were actually taken:

```json
{ "stationId": "KJFK", "temperatureC": 20, "windGustKmh": null,
  "fieldsMeasured": 8, "fieldsMissing": 1 }
```

If a station returns an observation with **no** measured values at all, that is not reported as a success — you get a row explaining it instead.

### What you get

| Field | |
|---|---|
| `stationId` / `stationName` / `elevationM` | which station reported |
| `observedAt` | when the observation was taken (ISO) |
| `textDescription` | `Clear`, `Mostly Cloudy`, … as NWS words it |
| `temperatureC` / `temperatureF` / `dewpointC` / `dewpointF` | both units, `null` if unmeasured |
| `relativeHumidityPct` | |
| `windSpeedKmh` / `windGustKmh` / `windDirectionDeg` | |
| `barometricPressurePa` / `seaLevelPressurePa` / `visibilityM` | |
| `windChillC` / `heatIndexC` | only present when conditions call for them |
| `precipitationLast3HoursMm` / `maxTemperatureLast24HoursC` / `minTemperatureLast24HoursC` | |
| `rawMessage` | the original METAR string, if the station sends one |
| `fieldsMeasured` / `fieldsMissing` | how much of this row is real |
| `resolvedFromPoint` | set when you gave coordinates instead of a station id |
| `checkedAt` | when this Actor asked |

### Input

```json
{ "stations": ["KJFK", "KORD", "38.89,-77.03"], "maxRetries": 3 }
```

| Input | |
|---|---|
| `stations` | NWS station ids (`KJFK`) or points as `"lat,lon"`. A point costs two extra requests while the nearest station is resolved, and the row records which point it came from. |
| `maxRetries` | Retries when NWS rate-limits or has an outage. |

An input that cannot be read — `"Tokyo"`, `"K1"` — produces a row saying exactly that, and **no request is sent to NWS**.

Measured on 2026-08-30: `KJFK`, `KORD` and `KSEA` all returned observations; a point in Washington DC resolved to `KDCA` out of 54 nearby stations.

### Billing

Charged per observation delivered. Rows that explain a bad input, a missing station, or an NWS outage are free. If you set a maximum total charge on the run and it is reached, the run stops and says so in the log and the run status rather than handing you a partial result that looks complete.

### Source and conduct

Data comes from the National Weather Service public API. NWS states the information is *"open data, free to use for any purpose"* and asks that clients identify themselves with a User-Agent; this Actor sends one that includes a contact URL, so NWS can reach us rather than block us if anything ever looks wrong.

# Actor input Schema

## `stations` (type: `array`):

NWS station ids such as KJFK, KORD, KSEA - or a point as "lat,lon" like 38.89,-77.03, in which case the nearest reporting station is found for you. Mix them freely.

## `maxRetries` (type: `integer`):

How many times to retry a station when NWS rate-limits or has an outage, before writing a row that says why.

## Actor input object example

```json
{
  "stations": [
    "KJFK"
  ],
  "maxRetries": 3
}
```

# Actor output Schema

## `results` (type: `string`):

All forecast rows produced by this run.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "stations": [
        "KJFK"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("neverempty/us-weather-observations").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "stations": ["KJFK"] }

# Run the Actor and wait for it to finish
run = client.actor("neverempty/us-weather-observations").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "stations": [
    "KJFK"
  ]
}' |
apify call neverempty/us-weather-observations --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,neverempty/us-weather-observations"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/KUK8h7fceZeoVZDjN/builds/9DHMShNhET4rVYGrg/openapi.json