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.
Past Storm Leads by Address returns address-level records of storm events reported or radar-detected at or near each address over the trailing 365 days. Filter by county, peril type and severity threshold.
Each record carries the address, coordinates, storm type, event time in UTC, a severity value with its unit (for example hail diameter in inches or wind speed in mph), distance from the event and a hit count for repeat exposure. Because some storm types report severity in more than one unit, the free preview exposes the units so filters never blend them. Records are sorted by severity, then recency.
Billing is $0.05 per returned address. The free preview shows counts, severity ranges, repeat-hit addresses and the exact price before you pay, and every paid response carries a reference_id receipt. This is a record of reported and radar-detected events, not a damage assessment.
Built by Atlas United. Not affiliated with NOAA or the NWS.
Highlights
Addresses near storms reported or radar-detected in the last 365 days, with event time, type, severity and unit, and distance.
Filter by county, peril and severity. Records sorted by severity then recency. Repeat-hit addresses flagged.
$0.05 per returned address. Free preview with counts, severity ranges and exact cost first.
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.
This listing uses one usage-based dimension: you pay per storm lead address returned. Each returned address record is a single billable unit. Pricing scales directly with how many address records your pull returns, so a larger set of addresses costs more and a smaller set costs less. There are no seats, no contracts, and no minimum term. You fund a prepaid balance and draw it down as you pull data. Free previews show counts and the exact cost before you spend. An identical repeat request within about two hours may be served from cache at no extra charge.
Top-of-mind questions for buyers
What exactly counts as one billable address record in a storm lead pull?
One billable unit is a single address record returned at or near a storm reported or radar-detected in the last 365 days. Each record carries the address, storm type, event time, severity with unit, distance, and a repeat-hit count. You pay for each returned record.
Can I limit how many addresses a pull returns to control cost?
Yes. You can filter by county, peril type, and measured severity so fewer addresses return. Filtering to one storm type or a higher severity reduces the records returned and lowers cost. A free preview shows counts, severity ranges, and the exact cost before you pull.
Does this listing include storm forecasts, weather conditions, or per-property history reports?
No. This listing bills only for past storm lead addresses from the last 365 days. Forecasts, point weather, hourly forecasts, and per-property history reports are separate products billed on their own units, not covered under this per-address dimension.
atlasunited.io+1
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
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
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.
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 Past Storm Leads 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=storms
POST <https://data.truefixr.com/v1/data> accepts the same parameters as a JSON body.
Returns address-level records of storms reported or radar-detected at or near each address over the last 365 days, filterable by county, peril and severity. A record means an event was reported or radar-detected near the address, not that damage occurred.
Query Parameters:
Param
Type
Description
dataset
string
storms (required)
county + state
string
County name and 2-letter state (required)
peril
string
Optional, for example HAIL, THUNDERSTORM_WIND, HEAVY_RAIN
min_severity, max_severity
number
Optional severity filters
addresses
boolean
true returns the paid address records. Omit for the free preview.
limit
int
Maximum addresses to return and bill, for example 10 for a 50 cent sample
offset
int
Paging offset. Use next_offset from the previous response.
Example Request (free preview, counts and exact cost):
Pricing: $0.05 per address returned. Billing unit: storm_lead_addresses.
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.
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.
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.
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.