# Locus: Property Scan – Groundwater Context

> Locus: Property Scan – Groundwater Context 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).

Scans local public records and parcel rules around a property location to surface answered groundwater-related questions, open issues, and recommended next verification steps.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-groundwater-context
- 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-groundwater-context-e4a69dad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_k4UpcBKaTqr3djBA7E42C

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-groundwater-context-e4a69dad -d '<json body>'
```

Example prompt: Can you run a Locus groundwater context scan on 4821 Elmwood Drive, Austin TX? Use a 3000-meter radius and tell me which public-record questions are already answered, which are still open, and what I should verify next.

## When to prefer this

Choose this endpoint when you need a fast, low-cost ($0.01) groundwater-specific public records scan tied to a specific property address or coordinate, particularly during early-stage real estate due diligence, site screening, or pre-decision research. It is most useful when you want to quickly identify what is already answered in public records versus what requires further investigation, rather than commissioning a full environmental report.

## Known failure modes

- Address not found or too ambiguous — returns empty records with coverage caveats
- Radius out of bounds (below 500m or above 25000m) — validation error
- No public records available for the given location — returns empty records array with explanatory caveats
- Coordinates outside supported geographic coverage — sparse or empty results
- Malformed address string (under 5 characters) — input validation rejection

## How this service works

USGS groundwater monitoring-well context for an address. Perfect for: 'groundwater depth near this property', 'nearby monitoring wells', 'what aquifer is near this address', 'historical water level observations'. Returns distance-banded monitoring wells, aquifer codes/names, reported construction depths, and static water levels. Not a domestic-well depth, yield, potability, contamination, or cost prediction. Charge-free unless state is data.

## Output

Returns a JSON artifact containing a scan ID, generation timestamp, a list of public record findings (records array), caveats about data completeness or coverage limitations, and guidance on which questions are answered versus still open or requiring 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",
   "default": 5000,
   "maximum": 25000,
   "minimum": 500
  }
 }
}
```

## 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-groundwater-context-e4a69dad/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)