gov.disaster-declarations

FEMA federal disaster & emergency declarations — every federally declared disaster since 1953, including the ones declared this week. Filter by state (2-letter), disasterNumber, declarationType (DR=major disaster, EM=emergency, FM/FS/FW=fire management), incidentType (e.g. Hurricane, Fire, Flood, Severe Storm), county (5-digit FIPS), fiscal year (fyDeclared), and declaration date range (fromDate/toDate, YYYY-MM-DD). With no filter, returns the most recent declarations nationwide. Returns the total matching count plus records (one per designated county/area) with the declaration string, disaster number, title, incident type, declaration + incident begin/end + closeout dates, designated area, county FIPS, FEMA region, and the assistance programs authorized (Individuals & Households, Individual Assistance, Public Assistance, Hazard Mitigation). Free, public-domain (OpenFEMA). Distinct from gov.risk-index (modeled future risk) and gov.nfip-claims (realized flood losses): this is the official federal-response record — for disaster-response logistics, eligibility checks, insurance, and emergency-management workflows.

price
$0.0018 USDC per call
method
GET/api/gov/disaster-declarations
payment
x402 v2 · USDC on Base (EIP-3009) or Solana (SPL transfer)
auth
None. Sign the payment, retry with PAYMENT-SIGNATURE.

Overview

The disaster declarations API is a pay-per-call gov endpoint built for AI agents and autonomous software. FEMA federal disaster & emergency declarations — every federally declared disaster since 1953, including the ones declared this week.

There is no signup and no API key. An agent (or any HTTP client) hits the endpoint, receives an x402 "402 Payment Required" challenge, signs a sub-cent USDC payment on Base or Solana, and retries — the data comes back on the paid request. That makes it a drop-in disaster declarations data source for an agent tool-use loop, an MCP host, or a backend that needs gov data on demand without onboarding to yet another vendor portal.

Use cases

Parameters

NameTypeDescription
statestring2-letter US state/territory code.
min 2 chars · max 2 chars
disasterNumberintegerFEMA disaster number.
min 1 · max 99999
declarationTypestringDR, EM, FM, FS, or FW.
min 2 chars · max 2 chars
incidentTypestringIncident type, e.g. Hurricane, Fire, Flood.
min 2 chars · max 60 chars
countystring
match ^\d{5}$
fyDeclaredinteger
min 1953 · max 2100
fromDatestring
match ^\d{4}-\d{2}-\d{2}$
toDatestring
match ^\d{4}-\d{2}-\d{2}$
limitinteger
min 1 · max 50

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/gov/disaster-declarations?state=xx&disasterNumber=1&declarationType=xx&incidentType=xx&county=12345&fyDeclared=1953&fromDate=2024-01-01&toDate=2024-01-01&limit=1'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/gov/disaster-declarations?state=xx&disasterNumber=1&declarationType=xx&incidentType=xx&county=12345&fyDeclared=1953&fromDate=2024-01-01&toDate=2024-01-01&limit=1' \
  -H 'PAYMENT-SIGNATURE: <base64-json-payload>'

# Or use the canonical runner (handles probe → sign → retry):
#   EVM_PRIVATE_KEY=0x... node --env-file=.env.local \
#     --experimental-strip-types scripts/x402-pay.ts \
#     'https://2s.io/api/gov/disaster-declarations?state=xx&disasterNumber=1&declarationType=xx&incidentType=xx&county=12345&fyDeclared=1953&fromDate=2024-01-01&toDate=2024-01-01&limit=1'
TypeScript / Node — @2sio/sdktypescript
import { TwoS } from '@2sio/sdk'

const client = new TwoS({
  privateKey: process.env.EVM_PRIVATE_KEY as `0x${string}`,
})

const result = await client.gov.disasterDeclarations({
  "state": "xx",
  "disasterNumber": 1,
  "declarationType": "xx",
  "incidentType": "xx",
  "county": "12345",
  "fyDeclared": 1953,
  "fromDate": "2024-01-01",
  "toDate": "2024-01-01",
  "limit": 1
})

console.log('endpoint:', result.endpoint)
console.log('cost:', result.costUsd, 'USDC')
console.log('tx:', result.settlement?.txHash)
console.log('data:', result.data)
Python — 2siopython
import os
from twosio import TwoS

client = TwoS(private_key=os.environ["EVM_PRIVATE_KEY"])

result = client.gov.disaster_declarations(state="xx", disasterNumber=1, declarationType="xx", incidentType="xx", county="12345", fyDeclared=1953, fromDate="2024-01-01", toDate="2024-01-01", limit=1)

print("endpoint:", result.endpoint)
print("cost:", result.cost_usd, "USDC")
print("tx:", (result.settlement or {}).get("tx_hash"))
print("data:", result.data)
MCP — Claude Desktop / AgentKit / any MCP hostjson
// 1. Add @2sio/mcp to your MCP host config (Claude Desktop example below).
//    EVM_PRIVATE_KEY funds x402 payments per call.

// claude_desktop_config.json
{
  "mcpServers": {
    "2sio": {
      "command": "npx",
      "args": ["-y", "@2sio/mcp"],
      "env": { "EVM_PRIVATE_KEY": "0x..." }
    }
  }
}

// 2. Once the server is running, agents call this tool via standard MCP:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "gov.disaster-declarations",
    "arguments": {
      "state": "xx",
      "disasterNumber": 1,
      "declarationType": "xx",
      "incidentType": "xx",
      "county": "12345",
      "fyDeclared": 1953,
      "fromDate": "2024-01-01",
      "toDate": "2024-01-01",
      "limit": 1
    }
  }
}

Response

FieldTypeDescription
queryobject
totalDeclarationsnumber
returnednumber
declarationsarray
sourceobject
notestring
Example response datajson
{
  "query": {
    "state": "example",
    "disasterNumber": 1,
    "declarationType": "example",
    "incidentType": "example",
    "county": "example",
    "fyDeclared": 1,
    "fromDate": "example",
    "toDate": "example",
    "limit": 1
  },
  "totalDeclarations": 1,
  "returned": 1,
  "declarations": [
    {
      "femaDeclarationString": "example",
      "disasterNumber": 1,
      "state": "example",
      "declarationType": "example",
      "declarationTypeLabel": "example",
      "declarationTitle": "example",
      "incidentType": "example",
      "declarationDate": "example",
      "fyDeclared": 1,
      "incidentBeginDate": "example",
      "incidentEndDate": "example",
      "disasterCloseoutDate": "example",
      "designatedArea": "example",
      "countyFips": "example",
      "region": 1,
      "tribalRequest": false,
      "programs": {
        "individualsAndHouseholds": false,
        "individualAssistance": false,
        "publicAssistance": false,
        "hazardMitigation": false
      }
    }
  ],
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "note": "example"
}

FAQ

Do I need an API key to use the disaster declarations API?
No. gov.disaster-declarations is x402-native — there is no signup and no API key. Your client makes the call, receives a 402 with payment requirements, signs a USDC payment, and retries. Funds come from a wallet you control.
How much does the disaster declarations API cost?
$0.0018 USDC per call, charged per request. There are no monthly fees, seats, or minimums — you pay only for the calls you make.
Can I try the disaster declarations API for free first?
Yes. Add ?trial=1 (or the header X-2s-Trial: 1) to get a free real call per endpoint per hour, so you can verify the response shape before wiring payment.
Which networks and tokens are supported?
USDC on Base (via EIP-3009 transferWithAuthorization) or Solana (SPL transfer), using the open x402 payment protocol.
How do I call gov.disaster-declarations from an AI agent or MCP host?
Use @2sio/sdk (TypeScript), 2sio (Python), or the @2sio/mcp server for any MCP host — each handles the probe → sign → retry loop for you. See the code samples on this page.

Discovery

Related: disaster declarations api · gov disaster declarations api · disaster declarations api for ai agents · x402 gov api · disaster declarations api no api key · pay per call disaster declarations api · gov api