Overview
What FloodPulse does
FloodPulse answers the climate risk questions that matter for real estate, insurance, and infrastructure decisions.
- GET /v1/flood?address=... returns the FEMA NFIP flood zone (AE, X, etc.), base flood elevation, whether the address is in a Special Flood Hazard Area, and the annual chance of flooding.
- GET /v1/wildfire?address=... returns the USFS Wildfire Hazard Potential (WHP) score and risk class for any US address.
- GET /v1/heat?address=... returns historical percentile counts for days above 90F, 95F, and 100F from the NOAA nClimGrid dataset (contiguous US only).
- GET /v1/report?address=... combines all three into a composite multi-hazard risk report with an overall risk score.
- GET /v1/compare?addresses=A|B returns a side-by-side comparison of two addresses across all three hazards.
Where the data comes from
Flood data comes from the FEMA National Flood Hazard Layer (NFHL). Wildfire data comes from the USFS Wildfire Hazard Potential dataset. Heat data comes from NOAA nClimGrid monthly averages. All sources are authoritative US government datasets. If a dataset is unavailable the API answers 503 and the call is not billed.
Three ways to connect
- REST with an X-API-Key header, described by an OpenAPI 3 schema (https://floodpulse.waltsoft.net/openapi.json ).
- MCP: five tools (getFloodRisk, getWildfireRisk, getHeatRisk, getFullReport, compareAddresses) on the Amazon Bedrock AgentCore Gateway.
- A2A (Agent2Agent 0.3): the agent card at https://floodpulse.waltsoft.net/.well-known/agent-card.json .
Billing
You pay per successful call on your AWS bill. Errors (400, 401, 404, 503) are never billed. Heat risk returns 404 for Alaska and Hawaii (NOAA nClimGrid covers contiguous US only).
Highlights
- Five climate hazard endpoints in one API: FEMA flood zone, USFS wildfire hazard potential, NOAA heat history, a composite multi-hazard report, and a side-by-side comparison of two addresses
- All government-authoritative data: FEMA NFHL for flood, USFS WHP for wildfire, NOAA nClimGrid for heat; if a source is unavailable the API returns 503 and nothing is billed
- Agent-ready: REST with an OpenAPI 3 schema, five MCP tools on Amazon Bedrock AgentCore Gateway, and an A2A agent card; pay only for successful calls
Details
Introducing multi-product solutions
You can now purchase comprehensive solutions tailored to use cases and industries.
Features and programs
Financing for AWS Marketplace purchases
Quick Launch
Pricing
Dimension | Description | Cost/unit |
|---|---|---|
API Call | Single API call to the service | $0.25 |
Vendor refund policy
No refunds for API calls already made. Contact support@waltsoft.net within 7 days of billing issues.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
- Amazon Bedrock AgentCore
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
FloodPulse MCP
FloodPulse is available as five MCP tools on the Amazon Bedrock AgentCore Gateway. Pass your api_key in every tool call.
Authentication
Pass your AWS Marketplace API key (mp_xxx) as api_key. No connection header needed.
Endpoint: MCP tool floodpulse___getFloodRisk
Returns FEMA flood zone and annual probability for a US address.
Example Request:
{ "tool": "floodpulse___getFloodRisk", "parameters": { "address": "1001 Texas Ave, Houston, TX", "api_key": "YOUR_API_KEY" } }Response Schema:
{ "hazard": "flood", "location": {"input": "1001 Texas Ave, Houston, TX", "lat": 29.76, "lon": -95.36}, "fema_flood_zone": {"zone": "AE", "special_flood_hazard_area": true}, "annual_chance": 0.01 }Available tools:
- floodpulse___getFloodRisk(address, lat, lon, api_key) — FEMA flood zone
- floodpulse___getWildfireRisk(address, lat, lon, api_key) — USFS wildfire hazard
- floodpulse___getHeatRisk(address, lat, lon, api_key) — NOAA heat history (contiguous US only)
- floodpulse___getFullReport(address, lat, lon, api_key) — full multi-hazard report
- floodpulse___compareAddresses(addresses, api_key) — side-by-side comparison
Gateway URL: <https://waltsoft-marketplace-gateway-xncyjgs1uh.gateway.bedrock-agentcore.us-east-1.amazonaws.com>
Error Codes
| Code | Meaning |
|---|---|
| 400 | Invalid or unrecognised US address |
| 401 | Invalid or inactive api_key |
| 404 | Data not available (heat: Alaska/Hawaii not covered by NOAA nClimGrid) |
| 503 | Upstream data source unavailable (not billed) |
Support
Vendor support
Contact support@waltsoft.net . Documentation:
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.