# Locus: Property Electricity Context Scan

> Locus: Property Electricity Context 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).

Retrieves electricity-related local records and parcel rules for a property address or geographic area, identifying answered and open public-record questions.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-electricity-context
- 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-electricity-context-scan-101b416f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Hl8aaUb3G0wncJ1hMartM

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-electricity-context-scan-101b416f -d '<json body>'
```

Example prompt: Can you run an electricity context scan on 742 Evergreen Terrace, Springfield — pull all local electricity records and parcel rules within 2000 meters and tell me what questions are answered, what's still open, and what I should verify next?

## When to prefer this

Use this endpoint when you need electricity-specific public records and parcel rule context for a property or area, particularly for real estate due diligence, utility planning, or solar feasibility research. Prefer this over generic property scan endpoints when the user's question is specifically about electricity regulations, utility infrastructure, or electricity-related parcel rules. Choose the radius parameter when area-level context matters more than a single parcel.

## Known failure modes

- Address not found or ambiguous — no records returned
- Radius too small or too large — outside the 1000–25000 meter allowed range
- No public records available for the specified area — empty records array with caveats
- Invalid coordinates — latitude or longitude out of bounds
- Missing required input — neither address nor lat/lng provided

## How this service works

Mapped HIFLD transmission-line proximity plus EIA statewide residential price context. Perfect for: data-center, industrial, energy-development, and power-sensitive site screens before utility diligence. Returns up to 10 lines and state price context; never a service, capacity, reliability, tariff, interconnection, timing, or cost finding. Charge-free when the point is unresolved and when neither source answers.

## Output

Returns a JSON artifact with a scan ID, timestamp, list of electricity-related public records for the queried area, applicable parcel rules, and caveats noting any data limitations or gaps. Also surfaces which questions are answered by public data and which remain open for manual 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
  },
  "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-electricity-context-scan-101b416f/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)