# Locus Renovation Site Context

> Locus Renovation Site Context is a paid API for AI agents from api.locus.report, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).

Aggregates parcel facts, permits, USDA soil data, terrain, FEMA flood zones, wetlands, and EPA radon data for a property address to support basement, addition, foundation, grading, drainage, waterproofing, or retaining-wall project planning.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-renovation-site-context
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/locus-renovation-site-context-dc2aec97
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_HZb0cQZVdNDeoG5Jc7qLq

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-renovation-site-context-dc2aec97 -d '<json body>'
```

Example prompt: Can you pull site context for 742 Evergreen Terrace, Springfield, IL before I start a basement waterproofing project — I want to see the FEMA flood zone, soil conditions, nearby permits, and radon context for that address?

## When to prefer this

Choose this endpoint when an agent or user needs pre-project public-record site context specifically for structural or drainage renovation work (basement, addition, foundation, grading, waterproofing, retaining wall) at a US property address. It uniquely bundles USDA soil, FEMA flood, wetland, terrain, radon, and permit data in a single call at low cost. Prefer it over general property lookup endpoints when soil conditions, flood exposure, and environmental context are the primary concerns, and when the user does not yet need a feasibility conclusion, inspection, or cost estimate.

## Known failure modes

- Address not recognized or parcel not found — returns thin evidence with charged:false
- Source unavailable for one or more data layers (FEMA, USDA, EPA) — partial groups returned with state:source_unavailable
- Insufficient subject identity or physical land data — threshold.met:false with missing fields listed
- Malformed or too-short address input rejected by schema validation
- Project type missing or empty — required field not provided

## How this service works

Research one exact property before a basement, addition, foundation, grading, drainage, waterproofing, or retaining-wall project. The fixed workflow combines parcel facts, exact-subject permits, USDA soil interpretations, sampled terrain, FEMA flood, mapped wetlands, and EPA county radon context. No feasibility, condition, design, cost, value, or construction-readiness conclusion. Thin evidence is charge-free. npx @velinussage/locus-agent-skill add.

## Output

Returns a structured JSON response with grouped public-record evidence including parcel identity details, subject-property permit history, USDA soil interpretations, sampled terrain data, FEMA flood zone classification, mapped wetland presence, and EPA county-level radon context. Includes threshold metadata indicating which data components were answered and which were unavailable, caveats, and handoff suggestions. No feasibility, condition, design, cost, or construction-readiness conclusions are provided. Returns charge-free if insufficient evidence is found.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "maxLength": 240,
   "minLength": 5
  },
  "projectType": {
   "type": "string",
   "maxLength": 160,
   "minLength": 1
  },
  "suiteOrUnit": {
   "type": "string",
   "maxLength": 80,
   "minLength": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "kind": "transaction_follow_up",
  "state": "source_unavailable",
  "groups": [],
  "intent": "renovation_planning",
  "caveats": [
   "Example artifact; not live data."
  ],
  "charged": false,
  "subject": {},
  "boundary": "Public-record context only; not an inspection, design, permit, condition, cost, or feasibility conclusion.",
  "handoffs": [],
  "timeline": [],
  "threshold": {
   "met": false,
   "missing": [
    "subject_identity",
    "physical_land"
   ],
   "answeredGroups": 0,
   "answeredComponents": 0
  },
  "profileTitle": "Renovation Site Context",
  "callerContext": {},
  "followUpItems": [],
  "unansweredQuestions": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/locus-renovation-site-context-dc2aec97/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)