Sold by: Atlas United
One citable report of every storm event reported or radar-detected near a property since 2003, across 11 categories. Each line has date, type, magnitude, distance and county. $0.05 per line, $10 minimum.
Overview
Image
Product overview
Image
Sample response
Image
County map
Storm History by Address is one property's long record. It returns every storm event reported or radar-detected within a chosen radius, from 2003 to the present, across 11 categories: hail, wind, flood, lightning, tornado, hurricane, winter storm, extreme heat and cold, drought, wildfire and coastal.
The report is citable, with a reference ID. Each line gives the event date, type, magnitude with units where a measure exists, distance in miles and county. Significant thresholds are defined in the report: hail 0.75 inches, wind 50 mph, winter storm 6 inches. An optional date_of_loss mode answers whether an event was reported or radar-detected near the address on a date, and lists events before and after it.
Pricing is $0.05 per report line with a $10 minimum per report. The free preview shows the exact line count and price before you pay. This is a record of reported and radar-detected events, not a damage assessment, and it does not support or dispute any claim.
Built by Atlas United. Not affiliated with NOAA or the NWS.
Highlights
- Every storm event reported or radar-detected near a property from 2003 to today, across 11 event categories, in one citable report.
- Optional date-of-loss mode: was an event reported or radar-detected near the address on that date, plus events in the 3 days before and after.
- $0.05 per line, $10 minimum. Free preview shows line count and exact price first.
Details
New
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
Dimension | Description | Cost/unit |
|---|---|---|
History report lines | One report line. Each report has a $10 minimum (200 lines) | $0.05 |
Dimensions summary
This listing uses one usage-based dimension billed per report line. You pay for each line returned in a storm history report for an address. Each report carries a minimum charge equal to 200 lines, so short reports still bill at that floor. Costs scale with the number of event lines you pull. You draw charges from a prepaid balance, and free previews show the exact cost before you commit. There are no seats, contracts, or minimum terms.
Top-of-mind questions for buyers
Each line is one reported or radar-detected storm event matched to the address. Lines span 11 event categories, including hail, wind, flood, lightning, tornado, hurricane, winter storm, extreme heat and cold, drought, wildfire, and coastal. Every line carries date, type, magnitude, distance, and county.
A per-report minimum applies. Each report bills at a floor equal to 200 lines, even when fewer lines are returned. Once a report exceeds that floor, you pay per line above it. Free previews show the exact cost before you pull the report.
An identical request made again within about two hours may be served from cache at no extra charge. Address-level records draw from a prepaid balance at the price shown when you request them. Outside the cache window, repeat pulls bill normally.
atlasunited.io
Helpful?
Vendor refund policy
Usage is billed only for records returned to you. If a response was billed in error, such as a failed pull or a duplicate charge, contact us within 30 days with the reference_id from the response and we will review it and refund or credit the billed usage. Records already delivered and correctly billed are not refundable. Contact: https://atlasunited.io/api
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA) .
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
Delivery details
API-Based Agents & Tools
API-Based Agents and Tools integrate through standard web protocols. Your applications can make API calls to access agent capabilities and receive responses.
Additional details
Usage instructions
API
To get started with Storm History by Address, follow the instructions below.
Prerequisites An active subscription to this listing on AWS Marketplace and any HTTP client or AI agent with HTTP access.
Authentication
- After you subscribe, choose "Set up your account" and finish the short form. Your API key is shown once on that page. If you lose it, choose "Set up your account" again in AWS Marketplace to get a new key; the old key stops working.
- Send the key on every paid request in this HTTP header: Authorization: Bearer YOUR_API_KEY Replace YOUR_API_KEY with your actual key. Free previews need no key.
Endpoint: GET <https://data.truefixr.com/v1/data> with dataset=history POST <https://data.truefixr.com/v1/data> accepts the same parameters as a JSON body. Use POST to keep the address and date of loss out of URLs and logs. Returns reported and radar-detected storm events near an address since 2003, across 11 categories: hail, wind, flood, lightning, tornado, hurricane, winter storm, extreme heat or cold, drought, wildfire and coastal. It shows what was reported near the address, not whether damage occurred.
Query Parameters:
| Param | Type | Description |
|---|---|---|
| dataset | string | history (required) |
| address | string | Street address (required), or use lat + lon |
| radius_mi | number | Search radius in miles (default 5) |
| date_of_loss | string | Optional YYYY-MM-DD. Adds a yes or no on whether an event was reported or radar-detected near the address on that date, plus events just before and after. |
| addresses | boolean | true returns the paid report. Omit for the free preview. |
Example Request (free preview, shows line count and exact price):
curl -X POST <https://data.truefixr.com/v1/data> -H "Content-Type: application/json" \ -d '{"dataset":"history","address":"891 Lake Hollow Blvd SW, Marietta, GA 30064"}'Example Request (paid report):
curl -X POST <https://data.truefixr.com/v1/data> -H "Content-Type: application/json" \ -H "Authorization: Bearer YOUR_API_KEY" \ -d '{"dataset":"history","address":"891 Lake Hollow Blvd SW, Marietta, GA 30064","addresses":true}'Response Schema (free preview):
{"dataset":"history","coordinate":{"lat":number,"lon":number},"radius_mi":number,"geocoded_address":"string", "real_line_count":number,"estimated_cost_usd":number,"by_peril":{"hail":number,"wind":number,"flood":number}}Response Schema (paid): the full report with every matched event grouped by peril, a reference_id receipt and, when date_of_loss is sent, a formatted citable report (report_markdown). Pricing: $0.05 per report line, with a $10.00 minimum per report. Billing unit: history_report_lines.
Error Codes
| Status | Code | Meaning |
|---|---|---|
| 400 | bad_request | A required parameter is missing or invalid. The detail field says which. |
| 401 | unauthorized | The key is not valid. |
| 402 | payment_required | A paid pull was requested without a valid key or enough prepaid balance. |
| 404 | not_found | No data for that location or filter. |
| 422 | invalid_parameter | A parameter value is not accepted. The response names the field and accepted values. |
| 429 | rate_limited | Too many requests. Wait and retry with exponential backoff. |
| 500, 502, 503 | server_error | Temporary server problem. Retry later. |
Error responses follow this structure: {"detail": "dataset=risk needs county+state, or lat+lon", "code": "bad_request", "request_id": "f38f7e69f7fb4ad4"} Quote the request_id (or the reference_id on a paid response) in a support request.
Learn More Docs: https://atlasunited.io/api Menu of every dataset, parameter and price: GET https://data.truefixr.com/v1/data MCP server for AI agents: https://mcp.atlasunited.io/mcp
Support
Vendor support
Support: https://atlasunited.io/api (docs, pricing, free previews). Email support is answered by the Atlas United team on business days. Every paid response carries a reference_id receipt you can quote in a support request.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Similar products
Address-level records of storms reported or radar-detected near each address in the last 365 days, filterable by county, peril and severity. $0.05 per address. Free preview shows counts and cost.
Probabilistic address-level storm forecasts from per-peril machine-learning models, 24 hours to 10 days ahead, refreshed 4 times a day. Each address carries its structure replacement value and people. $0.05 per address.
The Storm Events Database is an integrated database of severe weather events across the United States from 1950 to this year, with information about a storm event's location, azimuth, distance, impact, and severity, including the cost of damages to property and crops. It contains data documenting: The occurrence of storms and other significant weather phenomena having sufficient intensity to cause loss of life, injuries, significant property damage, and/or disruption to commerce. Rare, unusual, weather phenomena that generate media attention, such as snow flurries in South Florida or the San Diego coastal area. Other significant meteorological events, such as record maximum or minimum temperatures or precipitation that occur in connection with another event. Data about a specific event is added to the dataset within 120 days to allow time for damage assessments and other analysis.
The Multi-Year Reanalysis of Remotely Sensed Storms (MYRORSS) consists of radar reflectivity data run through the Multi-Radar, Multi-Sensor (MRMS) framework to create a three-dimensional radar volume on a quasi-Cartesian latitude-longitude grid across the entire contiguous United States. The radar reflectivity grid is also combined with hourly forecast model analyses to produce derived products such as echo top heights and hail size estimates. Radar Doppler velocity data was also processed into two azimuthal shear layer products. The source radar data was from the NEXRAD Level-II archive and the model analyses came from NOAA's Rapid Update Cycle model. Radar reflectivity was quality controlled to remove non-weather echoes and the data set was manually quality contolled to remove errors as revealed through inspection of dai[...]
Customer reviews
No customer reviews yet
Be the first to review this product . We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.