# Locus Practitioner Read – Property Public Records Analysis

> Locus Practitioner Read – Property Public Records Analysis is a paid API for AI agents from api.locus.report, paid per call via x402, $0.29/call, status unknown (last checked 2026-10-12).

Fetches parcel, transfer, zoning, permit, flood, wetland, soil, and legislation records for a US address and synthesizes them into hedged analyst-style prose, citing the specific record behind each observation.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-practitioner-read?utm_source=zero.xyz
- Price: $0.29/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/locus-practitioner-read-property-public-records-analysis-47fd7815
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zbJwSO_qvg4nZjMj-nP2i

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-practitioner-read-property-public-records-analysis-47fd7815 -d '<json body>'
```

Example prompt: As a buyer, pull the Locus practitioner read for 742 Evergreen Terrace, Springfield, IL — I want to know what an experienced land analyst would make of the public records there, including zoning, permits, flood, and soil, within 500 meters.

## When to prefer this

Choose this endpoint when you need a synthesized, citation-backed analyst narrative across multiple public record types (parcel, zoning, permits, flood, wetland, soil, legislation) for a single US address, especially when a persona-aware framing is needed. Prefer it over raw data lookups when the output needs to be human-readable prose with each claim grounded in a named record. Use the batch portfolio endpoint instead when processing more than one address at a time.

## Known failure modes

- Address not found or unresolvable — returns error indicating no parcel match
- Address outside supported US coverage — returns unsupported region error
- Insufficient public records available for the address — response may be sparse or indicate data gaps
- Invalid persona enum value — returns validation error
- radiusMeters out of allowed range (100–1500) — returns validation error
- Payment failure via x402 protocol — call not processed

## How this service works

Hedged prose from cited property records for one place. Each reading names the confirming record; an optional question sets the audience and focus. No value, person motive, or buildability finding. Allow at least 60 seconds (90 recommended). If disconnected, retry the same request for the same payer with fresh valid payment within 15 minutes; no charge occurs for the disconnected run. npx @velinussage/locus-agent-skill add.

## Output

A structured prose narrative written from the perspective of an experienced land and property analyst, covering parcel data, ownership transfers, zoning, permit history, flood zone, wetland status, soil conditions, and nearby legislation. Each observation is hedged and explicitly names the public record that confirms it. No buildability calls, no valuation, no assessment of individual motives.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "maxLength": 200,
   "minLength": 5
  },
  "persona": {
   "enum": [
    "buyer",
    "owner",
    "seller",
    "investor",
    "renter",
    "lender",
    "developer",
    "commercial_tenant"
   ],
   "type": "string"
  },
  "question": {
   "type": "string",
   "maxLength": 300
  },
  "radiusMeters": {
   "type": "integer",
   "maximum": 1500,
   "minimum": 100
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "kind": "practitioner_read",
  "focus": {
   "source": "inferred"
  },
  "prose": "example",
  "timing": {
   "stages": {},
   "totalMs": 1,
   "recordsCached": false
  },
  "address": "1 E Edenton St, Raleigh, NC 27601",
  "caveats": [
   "example"
  ],
  "charged": true,
  "persona": {
   "source": "caller"
  },
  "readings": [
   {
    "id": "example",
    "title": "example",
    "status": "matched",
    "checkNext": "example",
    "recordRefs": [
     "example"
    ],
    "readingText": "example"
   }
  ],
  "catalogue": {
   "gated": 0,
   "evaluated": 0
  },
  "permitMix": {
   "coverage": "covered",
   "available": false
  },
  "recordRefs": [
   "example"
  ],
  "verifyNext": [
   {
    "url": "https://example.gov/record",
    "label": "example"
   }
  ],
  "generatedAt": "2026-01-15T00:00:00.000Z",
  "questionUse": {
   "focusGroup": "records",
   "personaFrom": "question"
  },
  "waterContext": {
   "citations": [
    "example"
   ],
   "violations": [
    {}
   ],
   "nonInference": "example",
   "pfasDetectionCount": 1,
   "violationCount12mo": 1
  },
  "catalogueVersion": "example",
  "readingsNotEvaluated": [
   {
    "id": "example",
    "reason": "example"
   }
  ]
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/locus-practitioner-read-property-public-records-analysis-47fd7815/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)
