# locus.report Electricity Context API

> locus.report Electricity Context API is a paid API for AI agents from locus.report, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-15).

Returns HIFLD transmission-line proximity data and EIA statewide residential electricity price context for a given US location, useful for power-sensitive site screening.

## Facts

- Endpoint: POST https://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-report-electricity-context-api-265d43d0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_5QLqaRX3QFGcP30rBYGKX

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-report-electricity-context-api-265d43d0 -d '<json body>'
```

Example prompt: Can you pull the electricity context for 123 Data Center Drive, Ashburn, VA — I need nearby transmission lines within 10,000 meters and the state residential electricity price, to screen this site before we move to utility diligence?

## When to prefer this

Choose this endpoint when you need a fast, low-cost preliminary power infrastructure screen for US site selection — especially for data centers, industrial facilities, energy development, or any power-sensitive use case. It is ideal as a pre-diligence filter before engaging utilities directly, since it surfaces objective proximity and price context from authoritative federal sources (HIFLD, EIA). Do not use it when you need actual service availability, interconnection feasibility, capacity estimates, tariffs, or reliability data.

## Known failure modes

- Unresolved address or point outside US coverage — no charge, empty result returned
- Radius outside allowed range (1000–25000 meters) — validation error
- Neither HIFLD nor EIA has data for the location — returns empty with no charge
- Missing both address and lat/lng — request rejected
- Address geocoding failure — point cannot be resolved

## 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 up to 10 nearby HIFLD transmission lines with proximity metadata, plus EIA statewide residential electricity price context for the point's state. Does not include service availability, capacity, reliability, tariff, interconnection, timing, or cost findings. Returns no charge when the point is unresolved or neither data source has coverage.

## 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
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/locus-report-electricity-context-api-265d43d0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from locus.report](https://www.zero.xyz/host/locus.report/llms.txt)