Fema Disasters
by paylyte.ai in Other
New federal disaster declarations for a U.S. state or county, from the Federal Emergency Management Agency.
https://paylyte.ai/v1/data/fema/disasters- Price
- $0.5
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 269 ms
- 496 ms slowest 5%
- Last check
- Passed
- 34 min ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
GET https://paylyte.ai/v1/data/fema/disasters
Each call costs $0.5 in USDC on Base, 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://paylyte.ai/v1/data/fema/disasters?state=TXParameters
| Parameter | Type | Required | Description |
|---|---|---|---|
state | string | Yes | New federal disaster declarations for a U.S. state or county, from the Federal Emergency Management Agency. |
Example response
The provider's example. We can't check it without paying.
{
"as_of": "2026-05-01T00:00:00.000Z",
"attribution": "This product uses the Federal Emergency Management Agency's OpenFEMA API, but is not endorsed by FEMA. The Federal Government or FEMA cannot vouch for the data or analyses derived from these data after the data have been retrieved from the Agency's website(s).",
"county": "Harris",
"disasters": [
{
"area": "Harris (County)",
"declared": "2026-05-01",
"disasterNumber": 4781,
"incidentType": "Severe Storm",
"state": "TX",
"title": "Severe Storms",
"url": "https://www.fema.gov/disaster/4781"
}
],
"note": "Declarations as published by the Federal Emergency Management Agency (FEMA). Reports can lag the announcement.",
"product": "fema.disasters",
"retrievedAtUtc": "2026-10-16T18:00:00.000Z",
"since": "2026-01-01",
"sourceUrl": "https://www.fema.gov/api/open/v2/DisasterDeclarationsSummaries",
"state": "TX",
"tier": "fema"
}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.5.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://paylyte.ai/v1/data/fema/disasters?state=TX'
# 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://paylyte.ai/v1/data/fema/disasters?state=TX' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: 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.5 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.5" });
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.5 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fpaylyte.ai%2Fv1%2Fdata%2Ffema%2Fdisasters
const res = await pay("https://paylyte.ai/v1/data/fema/disasters?state=TX");
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.5 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.5"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.get("https://paylyte.ai/v1/data/fema/disasters?state=TX")
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
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 34 min ago | Passed | 402 | 273 ms | $0.5 |
| 4 h ago | Passed | 402 | 263 ms | $0.5 |
| 7 h ago | Passed | 402 | 417 ms | $0.5 |
| 10 h ago | Passed | 402 | 467 ms | $0.5 |
| 13 h ago | Passed | 402 | 228 ms | $0.5 |
Show 5 older checks
| 18 h ago | Passed | 402 | 321 ms | $0.5 |
| 23 h ago | Passed | 402 | 269 ms | $0.5 |
| 28 h ago | Passed | 402 | 217 ms | $0.5 |
| 33 h ago | Passed | 402 | 267 ms | $0.5 |
| 39 h ago | Passed | 402 | 496 ms | $0.5 |