# Locus: Property Scan – Noise & Proximity Records

> Locus: Property Scan – Noise & Proximity Records 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).

Runs a free scan of local public records and parcel rules for a given address, returning answered questions, open items, and next-step verification guidance focused on noise and proximity factors.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-noise-proximity
- 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-noise-proximity-records-6d799183
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_rGqwQlTRSbPmhnhJNzKCm

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-noise-proximity-records-6d799183 -d '<json body>'
```

Example prompt: Can you run a Locus property scan on 742 Evergreen Terrace, Springfield, IL — I want to see what public records say about noise and proximity issues and what still needs to be verified before I make an offer?

## When to prefer this

Choose this endpoint when you need a fast, free first-pass scan of public records and parcel rules for a specific property — particularly to surface noise and proximity signals before deeper due diligence. It is ideal as an early-stage screening step rather than a comprehensive title or environmental report.

## Known failure modes

- Address not found or not geocodable — returns empty records with caveats indicating no coverage
- Coordinates out of valid range — validation error on latitude/longitude bounds
- Address string too short or malformed — schema validation rejection
- No local records available for jurisdiction — returns empty records array with explanatory caveats
- Service unavailable or timeout — HTTP 5xx error with no result body

## How this service works

Research one property or compare a shortlist before a showing, offer, project, or tax appeal. Run free public-record checks, then buy deeper x402 reports with ready-to-run next steps.

## Output

Returns a JSON object with a scan ID, list of public-record findings keyed to the property, open questions that remain unanswered, caveats about data coverage, and a timestamp for when the report was generated.

## 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-noise-proximity-records-6d799183/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)
