# Model-Based Weather by Address: Conditions and Alerts (`truefixr_atlasunited/model-weather-by-address`) Actor

Send a street address or coordinates, get model-derived current conditions and active severe-weather alerts as one flat row per location. Includes a short-term rain outlook and a detailed multi-field pull. Flat rows for CSV or Excel.

- **URL**: https://apify.com/truefixr_atlasunited/model-weather-by-address.md
- **Developed by:** [Valentin Yslas](https://apify.com/truefixr_atlasunited) (community)
- **Categories:** Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 16.7% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 weather lookups

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?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Model-Based Point Weather and Alerts

**Model-derived current conditions and alerts for any US point, produced by our weather modeling pipeline. One detailed, flat row per location, ready for CSV, Excel, bots and agents.**

Values are modeled estimates for the exact coordinate, not readings from a nearby station.

### What you get

| Field | Meaning |
|---|---|
| `status` | `ok`, or `error` with an explanation (error rows are not charged) |
| `location`, `lat`, `lon` | The location as given and its coordinates |
| `observed_at` | Time the modeled conditions are valid for |
| `temperature_f`, `dewpoint_f` | Modeled air temperature and dew point (F) |
| `humidity_pct` | Modeled relative humidity (%) |
| `wind_speed_mph`, `wind_gust_mph`, `wind_direction_deg` | Modeled wind speed, gust and direction |
| `precip_in`, `precip_rate_inhr`, `precip_type` | Modeled precipitation amount, rate and type |
| `raining_now` | Whether the model indicates rain at the point now |
| `pressure_mb` | Modeled surface pressure (mb) |
| `visibility_mi` | Modeled visibility (miles) |
| `alert_count`, `alerts` | Number and text of active alerts at the point |

### Methodology

Conditions are derived from our weather modeling pipeline and sampled at the requested coordinate, so each field is a model estimate of the state of the atmosphere at that point and time. Rows are flat and typed so that they can be consumed directly by downstream code without parsing.

### Interpretation

Each value is a model-derived estimate for the point, not an observation from a physical instrument at that location, and it may differ from a nearby station. Alerts are informational context, not a safety determination.

### Input

```json
{ "locations": ["NYC", "Chicago", "30.27,-97.74"] }
```

`locations` accepts about 100 built-in major US city names, `lat,lon`, or `Label=lat,lon`. `maxChargeUsd` optionally caps spend. US locations only; unknown names return an error row, so use coordinates instead.

### Example record

```json
{ "status": "ok", "location": "Chicago", "temperature_f": 59.6, "humidity_pct": 74.5,
  "wind_speed_mph": 9.89, "wind_gust_mph": 13.08, "raining_now": false, "alert_count": 0 }
```

### Cost

Pricing is not enabled yet. The planned rate is $0.0002 per call (one location). Rows with `"status": "error"` are not charged.

### Compliance

This is data, not trading, insurance or safety advice. No guarantee of accuracy or results is made. Not affiliated with NOAA or the National Weather Service.

# Actor input Schema

## `locations` (type: `array`):

A full US street address (for example '1600 Pennsylvania Ave NW, Washington, DC'), a 'lat,lon' pair (for example '30.27,-97.74'), 'Label=lat,lon' to attach your own label, or a city name (for example 'Chicago', 'NYC'; about 100 major US cities are built in). Street addresses are geocoded for you and the geocoded address is returned in the row.

## `maxChargeUsd` (type: `number`):

Upper bound on the amount this run may charge once pricing is enabled. The planned rate is $0.0002 per location. Leave empty to rely on your Apify run budget.

## Actor input object example

```json
{
  "locations": [
    "New York",
    "Chicago",
    "Austin"
  ]
}
```

# Actor output Schema

## `dataset` (type: `string`):

No description

## `overview` (type: `string`):

No description

# 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 = {
    "locations": [
        "New York",
        "Chicago",
        "Austin"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("truefixr_atlasunited/model-weather-by-address").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 = { "locations": [
        "New York",
        "Chicago",
        "Austin",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("truefixr_atlasunited/model-weather-by-address").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 '{
  "locations": [
    "New York",
    "Chicago",
    "Austin"
  ]
}' |
apify call truefixr_atlasunited/model-weather-by-address --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,truefixr_atlasunited/model-weather-by-address"
        }
    }
}
```

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/Sk6vevmiH0tLJECHo/builds/NXQKt04D4BAmrcfVw/openapi.json