# 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-14).

Scans local public records and parcel rules for a given address or coordinates, revealing answered questions, open gaps, and recommended next verification steps.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-sole-source-aquifer
- 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-property-scan-a1abaeb3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kHroaI8ua1rR8E7cSlSZb

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

Example prompt: Can you run a Locus property scan on 742 Evergreen Terrace, Springfield, IL and tell me which public record questions come back answered, which are still open, and what I should verify next?

## When to prefer this

Use this endpoint when you need a fast, inexpensive ($0.01) first-pass scan of public records and parcel rules for a specific property before committing to deeper due diligence. It is ideal for pre-decision screening, quickly surfacing what is already known vs. what remains open, and guiding the next verification steps — especially when working at scale across many addresses or as the first step in a real estate research workflow.

## Known failure modes

- Address not found or too vague — returns empty records array with caveats noting insufficient location data
- Coordinates out of valid range (-90 to 90 lat, -180 to 180 lon) — input validation error
- No coverage for the given jurisdiction — records array empty with caveat explaining lack of local data
- Payment failure (x402) — 402 response before scan executes
- Malformed address string under 5 characters — schema validation rejection

## How this service works

EPA Sole Source Aquifer designation for an address. Perfect for: 'is this property in a Sole Source Aquifer', 'does EPA federal project review apply here', 'Sole Source Aquifer map lookup'. Returns mapped designation containment and Federal Register citations. The designation triggers EPA review of federally funded projects under SDWA 1424(e); it is not contamination, water quality, or a private-owner restriction. Charge-free when the snapshot is unavailable or stale.

## Output

Returns a JSON object with a scan ID, a list of public-record findings (records), any caveats about data coverage or freshness, and a timestamp (generatedAt). The records array details which public-record questions were answered, which remain open, and what steps to take next for verification.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "maxLength": 200,
   "minLength": 5
  },
  "latitude": {
   "type": "number",
   "maximum": 90,
   "minimum": -90
  },
  "longitude": {
   "type": "number",
   "maximum": 180,
   "minimum": -180
  }
 }
}
```

## 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-a1abaeb3/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)