13trust / 100

Water Flood Risk

by WaterPulse in Security & trust

x402 APIFailing, checked 5 h ago

Real-time flood risk for insurance and emergency-planning agents. Combines USGS stream gauges, Open-Meteo precipitation forecasts, and FEMA flood-zone context into current river conditions and actionable guidance.

GET
https://waterpulse.theaslangroupllc.com/api/water/flood-risk
Price
$0.15
per call in USDC
Uptime
0.0%
last 30 days
Response time
-
no timed checks yet
Last check
Failed
5 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Latest check failed 5 h ago: Amount "0.15" is not in atomic token units

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://waterpulse.theaslangroupllc.com/api/water/flood-risk

Each call costs $0.15 in USDC on Polygon, paid with the request over x402.

Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.

Example request

From the listing.

GET https://waterpulse.theaslangroupllc.com/api/water/flood-risk?lang=en&state=TN

Parameters

ParameterTypeRequiredDescription
langstringNoen | es | fr | de | ja | zh | ko | pt | ar (default: en)
locationstringNoCity, county, or river name — e.g. "Nashville TN" | "Mississippi River Iowa" | "Houston Harris County"
statestringNoTwo-letter US state code for USGS data enrichment — e.g. TN | IA | TX

Example response

The provider's example. We can't check it without paying.

Example response, 38 lines
{
  "current_conditions": {
    "action_stage_ft": 30,
    "condition": "Below action stage — monitoring recommended",
    "flood_stage_ft": 40,
    "pct_of_flood_stage": 71,
    "primary_river": "Cumberland River",
    "stage_ft": 28.4
  },
  "property_guidance": {
    "fema_zones_at_risk": [
      "AE",
      "AO"
    ],
    "nfip_note": "22% of Nashville flood claims come from outside high-risk zones. Consider coverage if within 1 mile of Cumberland or major tributary.",
    "preparation_checklist": [
      "Move valuables above ground level",
      "Test sump pump",
      "Locate flood shutoffs",
      "Review NFIP policy limits"
    ]
  },
  "query_summary": {
    "location": "Nashville TN",
    "risk_horizon": "72 hours",
    "state": "TN"
  },
  "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",
    "precipitation_72h_in": 2.1,
    "soil_saturation": "High (>85%) — upstream of Cordell Hull Dam"
  }
}

Call it from code

The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.15.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://waterpulse.theaslangroupllc.com/api/water/flood-risk?lang=en&state=TN'

# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - 'https://waterpulse.theaslangroupllc.com/api/water/flood-risk?lang=en&state=TN' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

// Pays at most $0.15 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.15" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);

// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.15 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fwaterpulse.theaslangroupllc.com%2Fapi%2Fwater%2Fflood-risk
const res = await pay("https://waterpulse.theaslangroupllc.com/api/water/flood-risk?lang=en&state=TN");
console.log(res.status, await res.text());
Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client

# Pays at most $0.15 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.15"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://waterpulse.theaslangroupllc.com/api/water/flood-risk?lang=en&state=TN")
    print(res.status_code, res.text)

Security scan

No findings

We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks

WhenResultHTTPTimePrice
5 h agoAmount "0.15" is not in atomic token units402181 ms$0.15
11 h agoAmount "0.15" is not in atomic token units4021.1 s$0.15
17 h agoAmount "0.15" is not in atomic token units402181 ms$0.15
23 h agoAmount "0.15" is not in atomic token units402342 ms$0.15
28 h agoAmount "0.15" is not in atomic token units402237 ms$0.15
Show 5 older checks
33 h agoAmount "0.15" is not in atomic token units402222 ms$0.15
39 h agoAmount "0.15" is not in atomic token units402205 ms$0.15
44 h agoAmount "0.15" is not in atomic token units402212 ms$0.15
2 days agoAmount "0.15" is not in atomic token units402180 ms$0.15
2 days agoAmount "0.15" is not in atomic token units402168 ms$0.15