# Locus Property Scan

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

Scans local records, parcel rules, and risk signals for a property to reveal factors affecting its use, cost, plans, or future value.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-power-water-evidence-pack
- Price: $0.05/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-3c17809e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tkLlwWDViaB3CwLchALsk

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

Example prompt: Can you run a Locus property scan on 742 Evergreen Terrace, Springfield, IL and flag any zoning restrictions, local records, or risk signals within 1500 meters that might affect its use or resale value?

## When to prefer this

Choose this endpoint when you need a broad property intelligence scan covering local records, zoning/parcel rules, and risk signals in a single call — especially when doing pre-purchase due diligence, development feasibility checks, or rental compliance research. It is well-suited for geospatial queries where you have coordinates and a radius rather than just an address lookup. Prefer it over general web search when you need structured, records-based property data rather than narrative descriptions.

## Known failure modes

- Address not found or ambiguous — no records returned
- Coordinates out of supported geographic coverage area
- Radius too small (below 1000m) or too large (above 25000m) returns validation error
- Empty records array if no relevant local data exists for the area
- Rate limiting or payment failure if USDC balance is insufficient

## How this service works

Pre-development evidence for one US address or point: HIFLD mapped transmission lines, EIA-reported power plants, county public-water-system context, and the official FCC broadband map. Use for a site power/water evidence pass before a utility call. Never grid capacity, substation location, interconnection, service availability, timing, cost, or performance claims. npx @velinussage/locus-agent-skill add.

## Output

Returns a JSON object containing a scan ID, a list of records covering local data, parcel rules, and risk signals relevant to the queried property or area, a generatedAt timestamp, and any caveats about data completeness or limitations.

## 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
  },
  "radiusMeters": {
   "type": "integer",
   "maximum": 25000,
   "minimum": 1000
  }
 }
}
```

## 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-3c17809e/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)