gov.nfip-claims

FEMA National Flood Insurance Program (NFIP) claims history for a US location — the flood losses actually paid out in an area. Requires state (2-letter); optionally narrow by county (5-digit FIPS), ZIP, and yearOfLoss range (yearFrom/yearTo). Returns the total matching claim count plus recent redacted claim records (date of loss, county / census tract / ZIP, flood zone rated at time of loss, cause of damage, water depth, net building + contents payment in USD, building coverage, approximate lat/lon), largest net payout first (the notable losses). FEMA redacts the city field, so filter by county FIPS or ZIP. Free, public-domain (OpenFEMA). Distinct from geo.flood-zone (current SFHA designation) and gov.risk-index (modeled future risk): this is the realized loss track record — for insurance underwriting and property due diligence.

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

Overview

The nfip claims API is a pay-per-call gov endpoint built for AI agents and autonomous software. FEMA National Flood Insurance Program (NFIP) claims history for a US location — the flood losses actually paid out in an area.

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 nfip claims 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
staterequiredstring2-letter US state/territory code.
min 2 chars · max 2 chars
countystring
match ^\d{5}$
zipstring
match ^\d{5}$
yearFrominteger
min 1970 · max 2100
yearTointeger
min 1970 · max 2100
limitinteger
min 1 · max 50

Code samples

cURLbash
# 1. Probe with no auth → 402 envelope with PaymentRequirements
curl -sS 'https://2s.io/api/gov/nfip-claims?state=xx&county=12345&zip=12345&yearFrom=1970&yearTo=1970&limit=1'

# 2. Sign + retry with PAYMENT-SIGNATURE:
curl -sS 'https://2s.io/api/gov/nfip-claims?state=xx&county=12345&zip=12345&yearFrom=1970&yearTo=1970&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/nfip-claims?state=xx&county=12345&zip=12345&yearFrom=1970&yearTo=1970&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.nfipClaims({
  "state": "xx",
  "county": "12345",
  "zip": "12345",
  "yearFrom": 1970,
  "yearTo": 1970,
  "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.nfip_claims(state="xx", county="12345", zip="12345", yearFrom=1970, yearTo=1970, 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.nfip-claims",
    "arguments": {
      "state": "xx",
      "county": "12345",
      "zip": "12345",
      "yearFrom": 1970,
      "yearTo": 1970,
      "limit": 1
    }
  }
}

Response

FieldTypeDescription
queryobject
totalClaimsnumber
returnednumber
returnedSummaryobject
claimsarray
sourceobject
notestring
Example response datajson
{
  "query": {
    "state": "example",
    "county": "example",
    "zip": "example",
    "yearFrom": 1,
    "yearTo": 1,
    "limit": 1
  },
  "totalClaims": 1,
  "returned": 1,
  "returnedSummary": {
    "totalPaid": 1,
    "averagePaid": 1
  },
  "claims": [
    {
      "dateOfLoss": "example",
      "yearOfLoss": 1,
      "countyCode": "example",
      "censusTract": "example",
      "zipCode": "example",
      "state": "example",
      "ratedFloodZone": "example",
      "causeOfDamage": "example",
      "waterDepth": 1,
      "occupancyType": 1,
      "netBuildingPaymentUSD": 1,
      "netContentsPaymentUSD": 1,
      "totalAmountPaid": 1,
      "totalBuildingInsuranceCoverage": 1,
      "latitude": 1,
      "longitude": 1
    }
  ],
  "source": {
    "provider": "example",
    "url": "example",
    "license": "example"
  },
  "note": "example"
}

FAQ

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