# Locus FEMA Events Property Scan

> Locus FEMA Events Property Scan is a paid API for AI agents from api.locus.report, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Scans FEMA event records, parcel rules, and risk signals for a given US address or ZIP code to surface factors affecting a property's use, cost, or value.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-fema-events
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/locus-fema-events-property-scan-52090bce
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Mj_3SGE0TdX43iuiDF0B7

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 locus-fema-events-property-scan-52090bce -d '<json body>'
```

Example prompt: Can you run a Locus property scan on 742 Evergreen Terrace, Springfield, IL 62704 and tell me what FEMA events, parcel rules, or risk signals might affect that property?

## When to prefer this

Use this endpoint when you need a quick, low-cost property risk scan tied to FEMA event history and local parcel rules for a US address or ZIP code, especially during early-stage real estate research or due diligence. Prefer this over general property APIs when FEMA disaster event data and parcel-level risk signals are the primary concern.

## Known failure modes

- Address not found or unresolvable — returns empty records array with caveats
- Invalid or missing ZIP/address input — likely 400 error or empty result
- Payment not processed (x402 protocol failure) — request blocked before data returned
- No FEMA events on record for the location — returns empty records array
- Non-US address provided — likely no data returned or error

## How this service works

FEMA disaster history for an area. Perfect for: 'FEMA disaster declarations for a county', 'disaster history for an address', 'flood / hurricane / wildfire declarations near a place', 'NFIP claims history'. Returns cited FEMA disaster declarations plus NFIP flood-insurance claim history for the resolved county. National. Historical record context, not a forecast or a risk score. Charge-free when the FEMA lookup fails.

## Output

Returns a JSON object containing a report ID, a list of FEMA event records and risk signals associated with the property, any caveats about data completeness, and a timestamp indicating when the report was generated.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "zip": {
   "type": "string",
   "maxLength": 10,
   "minLength": 5
  },
  "state": {
   "type": "string",
   "maxLength": 2,
   "minLength": 2
  },
  "address": {
   "type": "string"
  },
  "latitude": {
   "type": "number",
   "maximum": 90,
   "minimum": -90
  },
  "longitude": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  },
  "countyFips3": {
   "type": "string",
   "maxLength": 3,
   "minLength": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "locus_example",
  "caveats": [
   "Example artifact; not live data."
  ],
  "records": [],
  "generatedAt": "2026-01-01T00:00:00.000Z"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/locus-fema-events-property-scan-52090bce/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.locus.report](https://www.zero.xyz/host/api.locus.report/llms.txt)