gov.disaster-assistance

FEMA disaster assistance dollars — how much federal aid was approved or obligated for a declared disaster, by place. program=individuals (default) returns Individuals & Households Program (IHP) approved housing assistance, one record per ZIP per disaster, with FEMA-approved repair/replace, rental, and other-needs dollars and valid-registration counts (tenancy=owner default, or renter). program=public returns Public Assistance funded-project summaries, one record per applicant (state/local government, tribe, or eligible nonprofit) per disaster, with the federally obligated grant amount and project count. Filter by disasterNumber (the join key to gov.disaster-declarations), state (2-letter), and zipCode (5-digit, IHP only); results are ordered by approved/obligated dollars, highest first, with the total matching count and a normalized approvedAmountUSD per record. Free, public-domain (OpenFEMA). Distinct from gov.disaster-declarations (which disasters were declared + what was authorized), gov.risk-index (modeled future risk), and gov.nfip-claims (flood-insurance losses): this is the realized federal-spend record — for disaster-recovery, grants, insurance, and emergency-management workflows.

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

Overview

The disaster assistance API is a pay-per-call gov endpoint built for AI agents and autonomous software. FEMA disaster assistance dollars — how much federal aid was approved or obligated for a declared disaster, by place.

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 assistance 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
programstring'individuals' (IHP, default) or 'public'.
one of: individuals | public
tenancystringFor program=individuals: 'owner' (default) or 'renter'.
one of: owner | renter
disasterNumberintegerFEMA disaster number.
min 1 · max 99999
statestring2-letter US state/territory code.
min 2 chars · max 2 chars
zipCodestring5-digit ZIP (IHP only).
match ^\d{5}$
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-assistance?program=individuals&tenancy=owner&disasterNumber=1&state=xx&zipCode=12345&limit=1'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/gov/disaster-assistance?program=individuals&tenancy=owner&disasterNumber=1&state=xx&zipCode=12345&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-assistance?program=individuals&tenancy=owner&disasterNumber=1&state=xx&zipCode=12345&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.disasterAssistance({
  "program": "individuals",
  "tenancy": "owner",
  "disasterNumber": 1,
  "state": "xx",
  "zipCode": "12345",
  "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_assistance(program="individuals", tenancy="owner", disasterNumber=1, state="xx", zipCode="12345", 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-assistance",
    "arguments": {
      "program": "individuals",
      "tenancy": "owner",
      "disasterNumber": 1,
      "state": "xx",
      "zipCode": "12345",
      "limit": 1
    }
  }
}

Response

FieldTypeDescription
queryobject
programstring
totalRecordsnumber
returnednumber
returnedSumApprovedUSDnumber
recordsarray
sourceobject
notestring
Example response datajson
{
  "query": {
    "program": "example",
    "tenancy": "example",
    "disasterNumber": 1,
    "state": "example",
    "zipCode": "example",
    "limit": 1
  },
  "program": "example",
  "totalRecords": 1,
  "returned": 1,
  "returnedSumApprovedUSD": 1,
  "records": [
    {
      "program": "example",
      "disasterNumber": 1,
      "state": "example",
      "county": "example",
      "approvedAmountUSD": 1,
      "tenancy": "example",
      "city": "example",
      "zipCode": "example",
      "validRegistrations": 1,
      "approvedForFemaAssistance": 1,
      "repairReplaceAmount": 1,
      "rentalAmount": 1,
      "otherNeedsAmount": 1,
      "applicantName": "example",
      "educationApplicant": false,
      "numberOfProjects": 1,
      "incidentType": "example",
      "declarationDate": "example"
    }
  ],
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "note": "example"
}

FAQ

Do I need an API key to use the disaster assistance API?
No. gov.disaster-assistance 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 assistance 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 assistance 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-assistance 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 assistance api · gov disaster assistance api · disaster assistance api for ai agents · x402 gov api · disaster assistance api no api key · pay per call disaster assistance api · gov api