About TrueFixR Storm Data API
TrueFixR Storm Data API provides address-level U.S. storm history, recent event records, and model-based weather and peril forecasts. It serves insurers, adjusters, property managers, and data or AI-agent builders through REST and MCP access.
Key features
- 01Storm history by address since 2003
- 02Recent storm records for addresses
- 03Forecasts for 10 perils
- 04Point weather and hourly forecasts
- 05County and peril filters
- 06Free previews and reference receipts
Use cases
- 01Review storm records around a property
- 02Screen addresses for forecast risks
- 03Check current weather and short-term rain
- 04Find recent storm leads by county
MCP support
The API is available through an MCP server for Claude, ChatGPT, and other compatible clients. It exposes storm, weather, and forecast datasets to MCP clients.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://mcp.atlasunited.io/mcpclaude mcp add --transport http truefixr-atlascast-truefixr https://mcp.atlasunited.io/mcp{"mcpServers":{"truefixr-atlascast-truefixr":{"type":"http","url":"https://mcp.atlasunited.io/mcp"}}}Open in Cursor{"servers":{"truefixr-atlascast-truefixr":{"type":"http","url":"https://mcp.atlasunited.io/mcp"}}}Open in VS Code{"mcpServers":{"truefixr-atlascast-truefixr":{"type":"http","url":"https://mcp.atlasunited.io/mcp"}}}{"mcpServers":{"truefixr-atlascast-truefixr":{"serverUrl":"https://mcp.atlasunited.io/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
6| Parameter | Type | Required | Description |
|---|---|---|---|
| lat | number | No | Latitude in decimal degrees. |
| lon | number | No | Longitude in decimal degrees. |
| days | integer | No | Look-back window in days where supported. |
| kind | string | No | dataset=at_risk only. Narrows to 'schools' or 'businesses'. |
| limit | integer | No | Max records on the real paid pull (default 2000, real per-dataset caps still apply -- e.g. storms caps at 5000). |
| peril | string | No | Storm/risk type filter. Used by dataset=storms and dataset=risk (narrows to one storm type -- use the exact names returned under storm_types in a free preview) and by dataset=at_risk (narrows to one peril bucket, a different real meaning -- check that dataset's own preview for its real values). Common storms/risk values: HAIL, THUNDERSTORM_WIND, FLASH_FLOOD, HEAVY_RAIN, FLOOD, TORNADO. |
| state | string | No | 2-letter US state code, e.g. TX. |
| county | string | No | County name without the word 'County', e.g. Dallas. |
| format | enum | No | Response format. json (default) or csv.json | csv |
| months | integer | No | dataset=storms only. Returns month-bucketed history totals instead of individual leads, for the last N months. |
| window | enum | No | dataset=risk only. Forecast window. Default 24h.24h | 48h | 3d | 5d | 7d | 10d |
| address | string | No | Street address, for dataset=address. |
| dataset | enum | No | Target dataset. Default storms.storms | risk | address | coverage | facilities | wildfire | at_risk | daily | history | weather | hazard_score |
| details | boolean | No | dataset=weather only (Model-Based Weather by Address). true = full current-conditions pull, billed $0.0002/call. false (default) = free lean response, no account needed. Equivalent to addresses=true for this dataset. |
| category | string | No | dataset=facilities only. Facility category filter. |
| counties | string | No | Comma-separated county names (max 15) plus state, for a multi-county rollup. Free preview only. |
| addresses | boolean | No | false = free preview. true = address-level records -- requires EITHER the user's own Atlas United Data API account key (Authorization header) OR an x402 payment (see x_payment param below); no account needed for the x402 path. |
| radius_mi | number | No | dataset=history only. Search radius in miles. Default 5, max 25. |
| x_payment | string | No | Optional. A signed x402 protocol payment payload (base64), used instead of an API key to pay for ONE address-level pull in USDC on Base network. If addresses=true and neither an API key nor x_payment is provided, the response is an HTTP 402 with full payment instructions (pay_to address, amount, network) an agent can act on to construct this payload and retry. |
| hours_ahead | integer | No | dataset=weather only (Model-Based Hourly Forecast by Address). Forecast 0-48h out instead of current conditions -- snaps to the nearest available forecast hour, response's forecast_hour_used says exactly what you got. |
| date_of_loss | string | No | dataset=history only. YYYY-MM-DD. Anchors the report around this date -- returns the real weather events recorded on and immediately around that date, for reference. Not a determination of whether any claim is valid. |
| max_severity | number | No | Maximum measured severity. |
| min_severity | number | No | Minimum measured severity (e.g. 1.5 = 1.5 inch hail). Check severity_by_type in a preview for the real unit. |
Details
From the project READMEAtlas United storm data API: ML forecasts and storm history for every U.S. address
Atlas United builds risk models for every U.S. address (latitude/longitude), with all the information inside each location. This repository documents the API: address-level storm forecasts for the next 24 hours to 10 days, plus every reported storm at that address back to 2003. Pay per address, no contract.
AtlasCast is Atlas United's forecasting model suite: probabilistic, address-level forecasts for 10 perils, refreshed 4 times a day. TrueFixR is the storm-data side: reported and radar-detected storm history by address. Not affiliated with NOAA or the NWS.
The five products
| # | Product | dataset= | Price |
|---|---|---|---|
| 1 | ML Storm Forecast by Address | risk | $0.05 per address |
| 2 | Model-Based Weather by Address | weather | Lean response free, $0.0002 per call with details=true |
| 3 | Model-Based Hourly Forecast by Address | weather with hours_ahead (0 to 48) | $0.0002 per call |
| 4 | Storm History by Address: Reported and Radar-Detected Events Since 2003 | history | $0.05 per event line, $10 minimum per report |
| 5 | Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days | storms | $0.05 per address |
Products 1 to 3 are model outputs. Products 4 and 5 are recorded events matched to addresses.
1. ML Storm Forecast by Address
Probabilistic, address-level forecasts for 10 perils (tornado, hail, wind, flash flood, heavy rain, winter, ice, coastal surge, hurricane and wildfire), 24 hours to 10 days ahead, refreshed 4 times a day. AtlasCast uses a separate machine-learning model for each peril. Models are trained and validated chronologically on held-out reported events, and inputs are restricted to information available at forecast issue time.
Each address record carries the structure replacement value and the estimated people at that address, plus storm type, forecast time, a risk label and a past-hit count. Replacement value is the cost to rebuild the structure, not market value. Windows: 24h, 48h, 3d, 5d, 7d, 10d. Filter by county, peril and window. A free preview shows counts, per-peril totals, a county-level grade as a teaser, and the exact cost first. Forecasts describe what could happen, not what will happen.
2. Model-Based Weather by Address
Point weather for any U.S. coordinate: current conditions, active severe weather alerts and a short-term rain outlook. The lean response is free with no account. Add details=true for the full pull of over 170 variables at $0.0002 per call.
3. Model-Based Hourly Forecast by Address
Add hours_ahead (0 to 48) to the weather dataset for forecast hours instead of current conditions. The response reports the hour actually used in forecast_hour_used. Forecast hours carry a smaller core set of fields. $0.0002 per call.
4. Storm History by Address: Reported and Radar-Detected Events Since 2003
One property's long record: every storm event reported or radar-detected within a chosen radius, 2003 to the present, across 11 categories (hail, wind, flood, lightning, tornado, hurricane, winter storm, extreme heat and cold, drought, wildfire, coastal). Each line has event date, type, magnitude where measured, distance in miles and county. Citable, with a reference_id. An optional date_of_loss mode shows whether an event was reported or radar-detected near the address on a date, and lists events before and after it. A record of reported and radar-detected events, not a damage assessment.
5. Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days
Address-level records of storm events reported or radar-detected at or near each address over the trailing 365 days, filterable by county, peril and severity. Each record has the event time (UTC), type, measured or radar-estimated severity with its unit, distance and a repeat-hit count. A free preview shows counts, severity ranges and the exact cost. Not a damage assessment.
Access
| Method | Best for |
|---|---|
| REST API | Prepaid API key (from $25), Authorization: Bearer <key> |
| MCP server | Claude, ChatGPT and other MCP-compatible AI clients |
| x402 | Autonomous AI agents: pay per request in USDC on Base, no account |
Same prices either way. Every dataset has a free preview that shows counts and the exact price before you pay. Every paid response carries a reference_id receipt, and an identical paid query within 24 hours is not billed twice.
Endpoint
GET https://data.truefixr.com/v1/data
POST https://data.truefixr.com/v1/data (same params as a JSON body, keeps addresses out of URLs)
| Param | Description |
|---|---|
dataset | risk, weather, history, storms, plus address, hazard_score, facilities, wildfire (county-level), at_risk, daily, coverage |
state / county | 2-letter state code / county name |
peril | Narrow by peril, for example HAIL, FLASH_FLOOD, HEAVY_RAIN, TORNADO |
window | risk only: 24h, 48h, 3d, 5d, 7d, 10d |
hours_ahead | weather only: 0 to 48 |
addresses | Omit for the free preview. true for the paid pull (weather uses details=true) |
limit | Max records returned (limit=10 on a $0.05 dataset is a 50 cent sample) |
format | json or csv |
Call the endpoint with no params for the live machine-readable menu. Full detail per dataset: Datasets.
Batch endpoints
| Endpoint | Max locations | Price |
|---|---|---|
POST /v1/weather/batch | 500 | $0.0002 per location |
POST /v1/portfolio/risk | 500 | $0.05 per location (county forecast status, not address-level) |
For AI agents
An agent with no API key and no human in the loop can pay per call with x402:
- Request a paid pull, for example
GET https://data.truefixr.com/v1/data?dataset=storms&county=Dallas&state=TX&addresses=true&limit=1. - Receive HTTP 402 with the exact price.
- Sign a USDC payment on Base (
eip155:8453) and retry with the payment header. - Receive the data. No signup, no key.
Manifest: /.well-known/x402.json. Agent docs: llms.txt.
Data honesty
- Forecasts describe what could happen, not what will happen.
- A storm reported or radar-detected near an address is not a property inspection, damage assessment or repair estimate.
structure_valueis replacement cost (what it costs to rebuild), not market value.- Not affiliated with NOAA or the NWS.
Who this is for
Insurers, adjusters, emergency management, property managers, restoration, solar, and data and AI-agent builders.
Documentation
- Datasets: every dataset, price, free preview and example
- Sample data: trimmed real responses
- Who this is for: use cases by audience
- What you get: the two views of every address, and data honesty
- Comparison
- Code examples: curl, Python, JavaScript, x402 and MCP
- Industry evidence
Links
- API docs and signup: https://atlasunited.io/api and https://truefixr.com/api
- MCP server: https://mcp.atlasunited.io/mcp
- Company: https://truefixr.com
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.