# srch.best Disasters Data API

> srch.best Disasters Data API is a paid API for AI agents from x402.srch.best, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Returns structured FEMA/government disaster incident records filtered by state, date range, and incident type, paginated via cursor

## Facts

- Endpoint: POST https://x402.srch.best/disasters
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/srch-best-disasters-data-api-243bafb1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Dj4uTIratCHjVIxLK0RZu

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability srch-best-disasters-data-api-243bafb1 -d '<json body>'
```

Example prompt: Pull up to 20 disaster incident records for California between January 1, 2020 and December 31, 2023 — I want to see everything declared, starting with wildfires.

## When to prefer this

Use this endpoint when you need structured, paginated government disaster declaration data filterable by US state, date range, and incident type — especially in agentic workflows that require programmatic access with per-request micropayment via x402. Prefer this over web scraping FEMA.gov or unstructured search when you need clean, normalized records ready for downstream analysis.

## Known failure modes

- Invalid state code (not a 2-letter US abbreviation) returns a validation error
- Date format not matching ISO date (YYYY-MM-DD) causes a parse error
- Limit out of range (below 1 or above 50) returns a validation error
- Invalid or expired cursor causes a pagination error
- Payment failure via x402 results in a 402 Payment Required response
- No matching records for given filters returns an empty result set

## How this service works

Structured disasters data for agents, paid per request with x402 v2

## Output

A structured list of disaster incident records (up to 50 per page) including incident type, affected state, declaration dates, and an opaque cursor for fetching the next page of results.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "limit": {
   "type": "integer",
   "default": 10,
   "maximum": 50,
   "minimum": 1
  },
  "state": {
   "type": "string",
   "pattern": "^[A-Za-z]{2}$"
  },
  "cursor": {
   "type": "string",
   "maxLength": 128,
   "minLength": 1,
   "description": "Opaque continuation cursor returned by the previous response."
  },
  "toDate": {
   "type": "string",
   "format": "date"
  },
  "fromDate": {
   "type": "string",
   "format": "date"
  },
  "incidentType": {
   "type": "string",
   "maxLength": 80,
   "minLength": 2
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/srch-best-disasters-data-api-243bafb1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.srch.best](https://www.zero.xyz/host/x402.srch.best/llms.txt)