# WaterPulse Flood Risk API

> WaterPulse Flood Risk API is a paid API for AI agents from waterpulse-henna.vercel.app, paid per call via x402, $0.15/call, status unknown (last checked 2026-09-13).

Returns real-time flood risk assessments by combining USGS stream gauge data, Open-Meteo precipitation forecasts, and FEMA flood-zone context for a given location

## Facts

- Endpoint: GET https://waterpulse-henna.vercel.app/api/water/flood-risk
- Price: $0.15/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/waterpulse-flood-risk-api-775afe17
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9Xg11esL8sHnop5EahXE8

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability waterpulse-flood-risk-api-775afe17
```

Example prompt: What's the current flood risk near the Sacramento River at Sacramento, CA — I need the USGS gauge conditions, upcoming precipitation outlook, and FEMA flood zone context so I can decide whether to issue a flood warning for emergency planning.

## When to prefer this

Choose this endpoint when you need a synthesized, multi-source flood risk assessment that combines real-time stream gauge readings, precipitation forecasts, and regulatory flood zone context in a single call. Ideal for insurance underwriting, emergency planning agents, or property risk evaluation where actionable guidance is needed rather than raw hydrological data alone. Prefer over raw USGS or Open-Meteo APIs when you need integrated risk scoring rather than individual data streams.

## Known failure modes

- Location outside USGS gauge coverage returns no gauge data or partial results
- FEMA flood zone data unavailable for non-US locations
- Open-Meteo forecast unavailable for remote or offshore areas
- Invalid or unrecognized coordinates return a 400 error
- Upstream data source outage causes degraded or stale results
- Rate limiting or payment failure returns 402 or 429 error

## How this service works

Real-time water intelligence API. Groundwater levels, streamflow, drought status, water quality, aquifer analysis, flood risk, and global water stress — pay-per-query via x402.

## Output

Returns current river conditions from USGS stream gauges (flow rate, flood stage status), short-term precipitation forecasts from Open-Meteo, FEMA flood zone classification for the area, a composite flood risk level (e.g. low/moderate/high/extreme), and actionable guidance for insurance or emergency-planning decisions.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "lang": {
       "type": "string",
       "description": "en | es | fr | de | ja | zh | ko | pt | ar (default: en)"
      },
      "state": {
       "type": "string",
       "description": "Two-letter US state code for USGS data enrichment — e.g. TN | IA | TX"
      },
      "location": {
       "type": "string",
       "description": "City, county, or river name — e.g. \"Nashville TN\" | \"Mississippi River Iowa\" | \"Houston Harris County\""
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "errors": {
     "type": "object",
     "description": "Documented error responses, keyed by HTTP status code",
     "additionalProperties": {
      "type": "object",
      "required": [
       "description"
      ],
      "properties": {
       "example": {
        "type": "object"
       },
       "description": {
        "type": "string"
       }
      }
     }
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "query_summary": {
   "state": "TN",
   "location": "Nashville TN",
   "risk_horizon": "72 hours"
  },
  "risk_assessment": {
   "72h_outlook": "Moderate — 40-60% probability of reaching action stage",
   "current_risk": "Low-Moderate",
   "historical_context": "Cumberland River has exceeded 40 ft (flood stage) 6 times since 2000, including catastrophic 2010 event (51.9 ft)"
  },
  "upstream_factors": {
   "dam_releases": "Army Corps releasing 22,000 cfs at Old Hickory — elevated downstream levels expected",
   "soil_saturation": "High (>85%) — upstream of Cordell Hull Dam",
   "precipitation_72h_in": 2.1
  },
  "property_guidance": {
   "nfip_note": "22% of Nashville flood claims come from outside high-risk zones. Consider coverage if within 1 mile of Cumberland or major tributary.",
   "fema_zones_at_risk": [
    "AE",
    "AO"
   ],
   "preparation_checklist": [
    "Move valuables above ground level",
    "Test sump pump",
    "Locate flood shutoffs",
    "Review NFIP policy limits"
   ]
  },
  "current_conditions": {
   "stage_ft": 28.4,
   "condition": "Below action stage — monitoring recommended",
   "primary_river": "Cumberland River",
   "flood_stage_ft": 40,
   "action_stage_ft": 30,
   "pct_of_flood_stage": 71
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/waterpulse-flood-risk-api-775afe17/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from waterpulse-henna.vercel.app](https://www.zero.xyz/host/waterpulse-henna.vercel.app/llms.txt)