# Locus: Property Scan – Mitigation Incentives

> Locus: Property Scan – Mitigation Incentives 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-15).

Scans local public records and parcel rules to surface hazard-related mitigation incentives, flagging answered questions, open gaps, and next verification steps for a given address and hazard type.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-mitigation-incentives
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/locus-property-scan-mitigation-incentives-81404bc9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_l2lM95fPD8lAQ8IjCanz_

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-property-scan-mitigation-incentives-81404bc9 -d '<json body>'
```

Example prompt: Can you scan local records and parcel rules for 742 Evergreen Terrace, Springfield to see what flood mitigation incentives are available and what questions are still open?

## When to prefer this

Use this endpoint when you need a fast, low-cost ($0.01) lookup of local public-record mitigation incentives and parcel rules for a specific address and one of four supported hazard types (wind, wildfire, flood, earthquake). Prefer this over general web search when you want structured, record-level data with explicit coverage gaps flagged. Best suited for property research, pre-purchase due diligence, or insurance preparation workflows where knowing what's answered vs. open matters.

## Known failure modes

- Address not found or too ambiguous — returns empty records array with caveats
- Hazard type not one of the four supported enums (wind, wildfire, flood, earthquake) — schema validation error
- Place or address exceeds character limits — request rejected
- No local records exist for the specified parcel — returns empty records with explanatory caveats
- Transient data source unavailability — may return partial results or error

## How this service works

Cited mitigation grants, insurance-discount mandates, flood-map correction, and flood-protection rebate rows for a US place. Perfect for: 'home hardening grants', 'wind mitigation credits', 'flood mitigation incentives'. Optional hazard filter. Facts and money notes come from cited program rows only. No eligibility, savings, or premium estimate. Charge-free when no registry row returns.

## Output

Returns a JSON object with a scan ID, list of public-record findings (records array) covering applicable mitigation incentives and parcel rules, any caveats about data completeness, and a timestamp indicating when the scan was generated. Open questions and next-step verification guidance are surfaced within the records structure.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "place": {
   "type": "string",
   "maxLength": 200,
   "minLength": 1
  },
  "hazard": {
   "enum": [
    "wind",
    "wildfire",
    "flood",
    "earthquake"
   ],
   "type": "string"
  },
  "address": {
   "type": "string",
   "maxLength": 200,
   "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-property-scan-mitigation-incentives-81404bc9/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)