Got questions?
Good. Ask away.

ML Storm Forecast by Address (the forecast, $0.05 per address). Model-Based Weather by Address (free lean answer, $0.0002 per call for details). Model-Based Hourly Forecast by Address ($0.0002 per call). Storm History by Address: Reported and Radar-Detected Events Since 2003 ($0.05 per event line, $10 minimum per report). Past Storm Leads by Address: Reported and Radar-Detected, Last 365 Days ($0.05 per address). Every one has a free preview that shows the real price first.

Probabilistic, address-level storm forecasts, 24 hours to 10 days ahead, for 10 perils, from a separate machine-learning model for each peril. Each address record carries the structure replacement value (not market value) and the estimated people there, plus forecast time, storm type and risk label. $0.05 per address, refreshed 4 times a day. It describes what could happen, not what will happen. API: dataset=risk.

Address-level records of storms reported or radar-detected at or near each address in the last 365 days. Pick a county and a storm type. The count is free, with how many addresses had more than one storm reported nearby. The address list is $0.05 per address, and lists also come as CSV. API: dataset=storms.

Yes. You do not have to write any code. Open a page like claims, portfolio scans, property pages, spreadsheets or AI assistants, copy the "Just ask your AI" prompt, and paste it into Claude or ChatGPT. The AI explains each step in plain words, asks you for the address or file, and does the lookups. You stay in control: it checks the free preview and tells you the price before any paid call.

One property, one citable report of the storms reported or radar-detected near it since 2003, across 11 event categories (hail, wind, flood, lightning, tornado, hurricane, winter storm, extreme heat and cold, drought, wildfire and coastal). Other tools call the same kind of report a hail history report or a date of loss report. API: dataset=history. It costs $0.05 per event line with a $10 minimum per report, and the free preview shows the line count and the exact price first. It is a record of reported and radar-detected events, not an inspection and not a damage assessment.

AtlasCast is Atlas United's forecasting model suite: 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. It is the engine behind ML Storm Forecast by Address. Forecasts could happen, not will. TrueFixR does not send alerts; you can build your own from the records. Powered by atlasunited.io.

(In the API it is hazard_score.) The short form of Storm History by Address for one property. For each kind of event it shows how often it was reported nearby, the most recent one, the years since the last and, for hail, wind and winter, the most severe. It costs $0.50 per property, flat. A summary of reported and radar-detected events, not an underwriting decision.

You ask about an address, either by pasting a prompt into ChatGPT or Claude, or through your own software. You get the answer back. Every answer has a free preview that shows real counts and the real price first. Developers: send one request to https://data.truefixr.com/v1/data with a dataset name and a location, and add addresses=true and a key to pull full records.

Results are tied to the exact location you send, not a wide area. For storm history, events are matched to the property within about 150 meters. Send a latitude and longitude, or a street address for history.

A storm event was reported or detected on radar near that location. It is not an inspection and not a damage assessment. It says a storm was there, not what it did to any structure.

History is storms that were already reported or radar-detected. The forecast is storms that could happen in the coming days. It is probabilistic, and it is a forecast, not a promise. Forecast records lead with the structure value and people at each address. The county A to F grade you see in free previews is only a whole-county teaser, not a property score.

Ten: tornado, hail, wind, flash flood, heavy rain, winter, ice, coastal surge, hurricane and wildfire.

Model-Based Weather refreshes hourly. The ML storm forecast is refreshed 4 times a day. Storm history is reported and radar-detected events, up to 365 days back for storms, and 2003 to present for the history report. The free menu at GET /v1/data always has the current description of each dataset.

Call GET /v1/data?dataset=coverage. It is free, needs no key, and lists the states and counties that have data on file. Add state=TX to list one state's counties.

You add money to a prepaid balance. Each paid call takes its price off the balance. There are no plans, seats or contracts. See the price list for every route.

Weather data is free to download. A list of the storms that reached your address is not. Weather records say where a storm was, not which street addresses it touched, so someone has to do the matching. We do it for you. Ask about one address and get the storms reported or radar-detected near it, back to 2003, in one call. A lookup is a nickel, and the preview is free. Doing it yourself means building that matching, keeping it current and running it every day: an engineering project and a server bill before your first answer. If you want to own that, you do not need us. If you want the answer today, call the API. TrueFixR is not affiliated with NOAA or the National Weather Service.

Every dataset answers without a key. You see real counts and the real price before you pay. Coverage and daily are free always. The lean Model-Based Weather answer is free too.

A Storm History report has a $10.00 minimum, at $0.05 per event line. Everything else is billed per record with no minimum. A paid starting balance runs from $25 to $500.

Unauthenticated calls are limited to 60 per minute per IP address. Add your API key to the Authorization: Bearer header for key-based access.

HTTP 402 means payment is required. With a key, it means the pull needs a balance: top it up and call again. With x402, the response carries the price, and an x402 client pays and retries on its own.

Yes. If a key leaks, rotate it and the old one stops working right away. If you lose it, request recovery and it is emailed to the address on file. Both live on the get started page.

A way to pay per call with no account. Your agent pays in USDC on Base, call by call, using a standard x402 v2 client. The manifest is at https://data.truefixr.com/.well-known/x402.json. See for agents.

Yes. The MCP server at https://mcp.atlasunited.io/mcp works with Claude, ChatGPT, Cursor and other MCP clients. The OpenAPI spec is at https://data.truefixr.com/openapi.json.

Anyone who needs storm facts for an address: contractors, adjusters, insurance agents, property managers, small business owners, and the teams who build software for them.

Email [email protected].