# Locus Storm Events Property Scan

> Locus Storm 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-16).

Scans local records, parcel rules, and storm/risk signals for a US property address or ZIP code to surface factors affecting use, cost, and value.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-storm-events
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/locus-storm-events-property-scan-334e24a3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TD6hpY4_Rxo-fI5JbFV1Y

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-storm-events-property-scan-334e24a3 -d '<json body>'
```

Example prompt: Can you run a Locus property scan on 742 Evergreen Terrace, Springfield, IL 62704 and tell me about any local records, parcel rules, or storm risk signals that might affect its value or use?

## When to prefer this

Use this endpoint when you need a quick, low-cost property intelligence scan for a US address or ZIP code — especially for early-stage due diligence on real estate, checking zoning/parcel rules, or surfacing storm and risk signals before committing to deeper research. Prefer it over full appraisal or MLS services when a lightweight first-pass scan is sufficient.

## Known failure modes

- Invalid or unrecognized address returns empty records array with caveats
- Missing both address and zip fields returns a validation error
- Payment of 0.05 USDC not received results in 402 Payment Required
- Non-US addresses or international locations not supported
- Ambiguous address may resolve to wrong parcel or return no results

## How this service works

NOAA Storm Events history for a county. Perfect for: 'storm events for a county', 'hail / tornado / wind history for an area', 'NOAA severe weather records', 'past storm damage for a place'. Returns dated NOAA Storm Events Database records (1950-present): event type, date, damage estimates, and narrative for the county. National by point or state+county FIPS. Historical record context, not a forecast. Charge-free when the input does not resolve to a county or the NOAA fetch fails.

## Output

A JSON object containing a report ID, generation timestamp, an array of local records and risk signals found for the property, and any caveats about the data quality or coverage.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "place": {
   "type": "string",
   "maxLength": 200,
   "minLength": 2
  },
  "address": {
   "type": "string",
   "maxLength": 200,
   "minLength": 5
  },
  "endYear": {
   "type": "integer",
   "maximum": 9007199254740991,
   "minimum": 1950
  },
  "latitude": {
   "type": "number",
   "maximum": 90,
   "minimum": -90
  },
  "beginYear": {
   "type": "integer",
   "maximum": 9007199254740991,
   "minimum": 1950
  },
  "longitude": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  },
  "stateFips": {
   "type": "string",
   "maxLength": 2,
   "minLength": 1
  },
  "countyName": {
   "type": "string",
   "maxLength": 60,
   "minLength": 3
  },
  "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-storm-events-property-scan-334e24a3/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)