# Locus: Property Scan

> Locus: 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-15).

Scans local public records and parcel rules for a given address to show which questions are answered, what remains open, and what to verify next.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-program-windows
- 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-0d9a01af
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sxE6eBt6FOit6n7-qH5xH

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-0d9a01af -d '<json body>'
```

Example prompt: Can you run a Locus property scan on 742 Evergreen Terrace, Springfield, IL — use today's date and look back up to 120 days — and tell me which public-record questions are answered, which are still open, and what I should verify next?

## When to prefer this

Use this endpoint when you need a quick, low-cost public-records snapshot for a specific property address — especially during early-stage due diligence, pre-purchase research, or compliance checks — where you want to know both what is already on file and what gaps remain. It complements deeper paid data pulls by surfacing open questions first.

## Known failure modes

- Address not found or too ambiguous — returns empty records with caveats
- withinDays out of allowed range (1–400) — validation error
- asOf date in wrong format or invalid calendar date — schema validation failure
- No local records available for the jurisdiction — returns records:[] with explanatory caveats
- Payment failure (x402) — request blocked before processing

## How this service works

Exact dated owner-program windows for a US place. Perfect for: 'program deadlines in the next 180 days', 'which property program dates recently passed'. Deterministically filters exact ISO dates printed in cited registry rows; it does not infer dates from narrative rules. Charge-free when no upcoming or recently passed item returns.

## Output

A JSON object containing a scan ID, the date the scan was generated, a list of public-record findings (records array), and any caveats about data completeness or freshness — showing which questions are answered, which remain open, and what still needs verification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "asOf": {
   "type": "string",
   "format": "date",
   "pattern": "^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))$"
  },
  "place": {
   "type": "string",
   "maxLength": 200,
   "minLength": 1
  },
  "address": {
   "type": "string",
   "maxLength": 200,
   "minLength": 1
  },
  "withinDays": {
   "type": "integer",
   "default": 120,
   "maximum": 400,
   "minimum": 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-0d9a01af/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)