FEMA Flood & Climate Risk Report for Any US Home avatar

FEMA Flood & Climate Risk Report for Any US Home

Pricing

from $6.00 / 1,000 property risks

Go to Apify Store
FEMA Flood & Climate Risk Report for Any US Home

FEMA Flood & Climate Risk Report for Any US Home

Cross-check flood, fire, heat and wind risk for any US property. Compare the home-level climate score with the ZIP-level climate score and flag disagreements. Returns FEMA flood zone, insurance flags, heat-day forecasts and a per-hazard verdict. Address, ZPID or coordinates.

Pricing

from $6.00 / 1,000 property risks

Rating

0.0

(0)

Developer

SIÁN OÜ

SIÁN OÜ

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

4 days ago

Last modified

Share

Climate Risk Report — FEMA Flood, Fire, Heat & Wind 🚀

SIÁN Agency Store Sibling 1 Sibling 2 Sibling 3

🎉 Two public climate scores. One verdict. Disagreements stay visible.

For investors, insurers and agents who need a second opinion before they bind.

🔍 What is the Climate Environmental Risk Lens — and when should you use it?

The Climate Environmental Risk Lens turns one US address into a cross-checked flood, fire, heat and wind report. You get the home-level climate score and the ZIP-level climate score in the same row. Gaps are flagged, not merged.

Use it when you need: FEMA flood zone, flood/fire/heat/wind scores, insurance flags, heat-day forecasts, and an agree/disagree verdict per hazard.

Use something else when: you want comps, tax history and owner contact folded into the same row. Use Zillow Property Enrichment for that merged dossier.

🤖 Use with AI agents

Already connected to the Apify MCP server? Just ask for this Actor by name: sian.agency/climate-environmental-risk-lens

Otherwise copy this prompt into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want a climate risk report for a US home using the Apify Actor `sian.agency/climate-environmental-risk-lens`.
Use it when I need: FEMA flood zone, flood/fire/heat/wind scores, and a verdict that flags when the home score and the ZIP score disagree.
Don't use it when: I need comps, tax history or owner contact — use `zillow-property-enrichment-scraper` instead.
How to call it: pass one address (best), or a ZPID plus ZIP, or latitude and longitude.
Start with this input:
{
"address": "1875 Avondale Circle, Jacksonville, FL 32205"
}
Ask me for the street address or ZPID, then run the Actor and summarise flood, fire, heat and wind as a table with the verdict column first.

Things you can ask your agent for:

  • Score this Jacksonville address and tell me which hazards the two public scores disagree on.
  • Run these three Texas ZPIDs and list any FEMA zone other than X.
  • Give me heat-day now vs 30-year for this Austin home.

Machine-readable API, MCP config and OpenAPI definition for this Actor are published at apify.com/sian.agency/climate-environmental-risk-lens.md.

📋 Overview

You are looking at a second-opinion climate report — one US property, two public scores, a verdict per hazard.

Why teams use it:

  • Disagreements stay visible: the two scores are never silently merged
  • One address, one row: FEMA zone, four hazards, insurance flags
  • 🎯 Live probes, not guesses: Jacksonville fire disagrees; heat agrees at Extreme
  • 💰 Pay per scored property: failed lookups are not billed
  • 💎 Scale map included: home 1–10 and ZIP 0–5 land in the same 6 buckets
  • NEW: first SIÁN persona actor built only on climate data

✨ Features

  • 🌊 FEMA flood zone: X_UNSHADED and friends, straight from the home record
  • 🔥 Fire / wildfire score: home label plus ZIP homes-at-risk count
  • 🌡️ Heat path: hot days now and in 30 years
  • 💨 Wind and hurricane flag: insurance recommendation when the home score calls it critical
  • ⚖️ Per-hazard verdict: agree, lean-disagree, disagree, or single-source
  • 📮 ZIP or city fallback: a ZIP-only run still returns the neighborhood score
  • 📍 Coordinates: lat/lng reverse-geocode a ZIP for the ZIP-level half
  • 📄 Ledger report: risk scores in the hero, one fold per hazard

🎬 Quick Start

Paste an address. Run. Open the dataset.

curl -X POST https://api.apify.com/v2/acts/sian.agency~climate-environmental-risk-lens/runs?token=[YOUR_TOKEN] \
-d '{"address": "1875 Avondale Circle, Jacksonville, FL 32205"}'

🚀 Getting Started (3 Simple Steps)

Step 1: Open the actor

Find Climate Environmental Risk Lens on the SIÁN Agency Store.

Step 2: Paste a US address

Street, city, state and ZIP. A ZPID or listing URL works too.

Step 3: Run

The dataset row and the HTML report land together.

That's it! In under a minute, you'll have:

  • A verdict for flood, fire, heat and wind
  • Both raw scores, not a blended number
  • FEMA zone and insurance flags

📥 Input Configuration

FieldTypeRequiredDescription
addressstringNoFull US street address
zpidstringNoZillow property id
propertyUrlstringNoZillow listing URL
zipstringNo5-digit ZIP for the ZIP-level score
latitudestringNoDecimal latitude
longitudestringNoDecimal longitude
propertiesarrayNoBulk mix of the above

Example:

{
"address": "1875 Avondale Circle, Jacksonville, FL 32205"
}

Bulk Processing:

{
"properties": [
"1875 Avondale Circle, Jacksonville, FL 32205",
"10411 Turnbull Loop, Austin, TX 78717"
]
}

📤 Output

Results are saved to the Apify dataset with 40+ fields including:

FieldTypeDescription
overallVerdictstringagree, lean-disagree, disagree, single-source
femaZonestringFEMA flood zone
floodVerdictstringFlood cross-check
floodZillowScorenumberHome-level flood 1–10
floodRedfinScorenumberZIP-level flood 0–5
fireVerdictstringFire cross-check
heatVerdictstringHeat cross-check
windVerdictstringWind cross-check
zillowHeatDaysNownumberHot days this year
zillowHeatDays30ynumberHot days in 30 years

Example:

{
"address": "1875 Avondale Circle, Jacksonville, FL 32205",
"zip": "32205",
"overallVerdict": "disagree",
"femaZone": "X_UNSHADED",
"floodVerdict": "agree",
"floodZillowLabel": "MINIMAL",
"floodRedfinLabel": "Minor",
"fireVerdict": "disagree",
"fireZillowLabel": "MINIMAL",
"fireRedfinLabel": "Moderate",
"heatVerdict": "agree",
"heatZillowLabel": "EXTREME",
"heatRedfinLabel": "Extreme",
"windVerdict": "agree",
"coverage": "both",
"status": "success"
}

💼 Use Cases & Examples

1. Insurance pre-bind screening

An underwriter scores the subject property before a quote goes out.

Input: Street address with ZIP Output: FEMA zone plus four hazard verdicts Use: Hold the file if fire or wind is a disagree

2. Investor due diligence

An acquisitions analyst drops a ZPID from a bid list.

Input: ZPID and ZIP Output: Heat-day path and insurance flags Use: Price the cap-ex for cooling and wind

3. Listing risk disclosure

An agent attaches the report to a packet.

Input: Listing address Output: One-row verdict the buyer can read Use: Answer "is this in a flood zone?" without a portal login

4. Portfolio exception review

A risk team runs 50 addresses overnight.

Input: Bulk properties list Output: Filter overallVerdict=disagree Use: Manual review only where the two scores split

5. Underwriting second opinion

A desk already has one vendor score and wants the other public view.

Input: Address Output: Both raw scores, never a blend Use: Keep the disagreement as the signal

🔗 Integration Examples

JavaScript/Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('sian.agency/climate-environmental-risk-lens').call({
address: '1875 Avondale Circle, Jacksonville, FL 32205'
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('sian.agency/climate-environmental-risk-lens').call(
run_input={'address': '1875 Avondale Circle, Jacksonville, FL 32205'}
)
for item in client.dataset(run['defaultDatasetId']).iterate_items():
print(item)

cURL

curl -X POST 'https://api.apify.com/v2/acts/sian.agency~climate-environmental-risk-lens/runs?token=YOUR_TOKEN' \
-H 'Content-Type: application/json' \
-d '{"address": "1875 Avondale Circle, Jacksonville, FL 32205"}'

Automation Workflows (N8N / Zapier / Make)

  1. Trigger: New deal or scheduled book
  2. HTTP Request: Call this actor
  3. Process: Read overallVerdict
  4. Action: Slack the disagrees

📊 Performance & Pricing

FREE Tier (Try It Now)

  • 1 property per run — full verdict, same fields
  • No credit card required
  • Perfect for a single underwrite
  • Unlimited properties per run
  • Same cross-check, no extra setup
  • Pay-per-result: only charged for successful scores

💰 Report-shaped pricing — a small one-time report fee plus a cheap per-property event. The trial run stays cheap on purpose.

🔗 View current pricing

❓ Frequently Asked Questions

Q: How many properties can I score? A: FREE tier: 1 per run. PAID tier: unlimited.

Q: What if only one score comes back? A: The row is marked single-source. We do not invent the missing half.

Q: What output formats are available? A: JSON, CSV, Excel — export from the dataset. The HTML report is in the key-value store.

Q: Do I need a portal account? A: No. Paste an address. No API key of your own.

Q: Is this legal? A: Yes — we only return publicly shown climate scores. See our legal section.

Q: How long does one property take? A: Usually under 10 seconds.

Q: Why do the two fire numbers disagree in Jacksonville? A: They measure different things on different scales. That gap is the product.

🐛 Troubleshooting

ZIP-level score is missing

  • Add a 5-digit ZIP to the address
  • Or fill the ZIP field next to a ZPID

Home-level score is missing

  • Use a full street address, a ZPID or a listing URL
  • Coordinates alone only unlock the ZIP-level half

Empty dataset

  • Check the address is a real US home
  • Re-run just that property from the retry block in the report

Our actors are ethical and do not extract any private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. We therefore believe that our actors, when used for ethical purposes by Apify users, are safe.

However, you should be aware that your results could contain personal data. Personal data is protected by the GDPR in the European Union and by other regulations around the world. You should not scrape personal data unless you have a legitimate reason to do so. If you're unsure whether your reason is legitimate, consult your lawyers.

You can also read Apify's blog post on the legality of web scraping.

⚠️ Trademark Disclaimer

Zillow® and Redfin® are registered trademarks of their respective owners. This actor is not affiliated with, endorsed by, or sponsored by Zillow, Redfin, or First Street Foundation. All trademarks remain the property of their owners.

🤝 Support

Join our active support community


Built by SIÁN Agency | More Tools