Research a property

Research a property

Use this as a guided workflow, not a completed property report or a claimed test. It helps an agent gather cited public-record context for a decision. It does not provide a valuation, eligibility result, approval, legal outcome, title result, utility-service determination, development capacity, or safety label.

Start with two questions

Ask the user:

1. What exact property address should I research?
2. What decision will this research support?

If either answer is missing, ask and stop. Do not assume an address, add a jurisdiction, or make a tool call to fill the gap. If the address can resolve to more than one jurisdiction, ask the user to choose.

Run the free-first sequence

1. Load the current Locus agent skill.

2. Load the current Locus free tool catalog. The live catalog controls tool names, schemas, coverage, and payment rails.

3. Call locus_execute with the exact user address and detailLevel: "full":

   {
     "name": "locus_lane_availability",
     "arguments": {
       "place": "SUPPLIED_EXACT_ADDRESS",
       "detailLevel": "full"
     }
   }

   Replace SUPPLIED_EXACT_ADDRESS with the exact address the user supplied. Never send the placeholder or invent a different address. Use the catalog’s tool executor or the Locus MCP server. Availability is a capability and coverage map. It is not a property finding.

4. Select only relevant free tools from the live result. Depending on the decision and local coverage, these can include parcel, zoning, permit, tax, and development or planning records. Use each tool’s exact schema and jurisdiction.

5. For every result, preserve the source URL, observed date, jurisdiction, coverage status, and caveat. Label candidate, reported, partial, stale, unavailable, and not-verified information instead of turning it into a conclusion.

6. Stop before any paid call, subscription, or monitoring. If the user later requests an optional paid report, show its exact live challenge price, recipient wallet, network, asset, and scope. Ask for approval of that exact call. Do not use a cached wallet or fixed payment promise.

Copyable agent prompt

Run the Boon guided property-research workflow.

First ask me for (1) the exact property address and (2) the decision this
research will support. Do not assume an address, add a jurisdiction, scrape a
portal, or make a tool call until I answer both. If the address is ambiguous,
ask me to choose the jurisdiction.

After I answer, load https://docs.locus.report/skill.md and
https://api.locus.report/tools/list. Then call locus_execute with:
{"name":"locus_lane_availability","arguments":{"place":"<SUPPLIED_EXACT_ADDRESS>","detailLevel":"full"}}

Replace `<SUPPLIED_EXACT_ADDRESS>` with the exact address I supplied. Never send
the placeholder or invent a different address.

Treat availability as coverage metadata, not a finding. Use only the relevant
free Locus tools for parcel, zoning, permit, tax, and development or planning
records. Return source URLs, observed dates, jurisdictions, evidence labels,
coverage limits, and unknowns. Do not score, rank, value, predict, or label
anything safe or unsafe. Do not infer eligibility, approval, utility service,
capacity, ownership, title, or legal outcome. Do not make paid calls, start a
subscription, or set monitoring. If I later request a paid call, show its live
price, recipient, network, asset, and scope and ask for exact approval first.

Label the result: "Guided workflow; not a completed property report and not a
claimed test."

Download the skill

Download the machine-readable Boon property-research skill. It is generated from skill/boon-property-research/SKILL.md by the repository’s deterministic documentation sync.