# Locus Road Access Property Scan

> Locus Road Access 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-16).

Scans local records, parcel rules, and risk signals for a US property address or ZIP code to surface factors affecting use, cost, or value.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-road-access
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/locus-road-access-property-scan-0381762c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1xJBZNIhHp_DCZKrtkJbO

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-road-access-property-scan-0381762c -d '<json body>'
```

Example prompt: Can you run a Locus property scan on 742 Evergreen Terrace, Springfield, IL 62704 and tell me about any zoning rules, road access issues, or risk signals that might affect its use or value?

## When to prefer this

Use this endpoint when you need a quick, low-cost preliminary scan of US property records, parcel rules, and risk signals before committing to deeper due diligence. Ideal for early-stage property research, flagging issues with road access or zoning, or enriching a property listing with local data signals.

## Known failure modes

- Address not found or too ambiguous — returns empty records array
- Invalid or missing ZIP/address input — returns validation error
- Property outside US coverage area — returns empty or partial records
- Upstream local records unavailable — returns records array with caveats
- Payment not processed (x402) — request rejected before scan runs

## How this service works

Road-access screen for one US address or point: nearest mapped public road to the geocoded point. Road adjacency at the geocoded point, not parcel-boundary frontage; physical mapped-road only, never a legal access or landlocked determination. Perfect for: 'does this address have road access', 'nearest road to a property', 'is this parcel on a public road', 'rural/set-back access screen'. npx @velinussage/locus-agent-skill add.

## Output

A JSON object containing a scan ID, list of records from local databases, parcel and zoning data, risk signals, and a timestamp — along with any caveats about data completeness or 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": "number",
   "maximum": 2000,
   "minimum": 50
  }
 }
}
```

## 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-road-access-property-scan-0381762c/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)