# Locus Transaction Follow-Up Packet Builder

> Locus Transaction Follow-Up Packet Builder 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).

Builds a cited public-record follow-up packet for a specific real estate transaction intent (homebuyer, land investor, developer pre-development, or commercial tenant) after explicit profile confirmation.

## Facts

- Endpoint: POST https://api.locus.report/api/locus-transaction-follow-up
- 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-transaction-follow-up-packet-builder-e4035018
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_O8TzMIDlTxLOGGX-sSRvB

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-transaction-follow-up-packet-builder-e4035018 -d '<json body>'
```

Example prompt: I've confirmed I'm a homebuyer — can you pull a cited public-record follow-up packet for 742 Evergreen Terrace, Springfield, IL, for a single-family residential purchase I'm under contract on?

## When to prefer this

Use this endpoint when a user has explicitly confirmed one of the four supported transaction profiles (homebuyer, land investor, developer pre-development, or commercial tenant) and needs a structured, cited public-record follow-up checklist for a specific address at a known transaction stage. Prefer this over the general due-diligence bundle endpoint when the user is already engaged in a transaction and needs actionable next steps rather than a broad pre-decision overview. The intent-typed registry ensures only relevant evidence is included for each profile.

## Known failure modes

- Address not found or ambiguous — returns empty follow-up items with caveats
- Unsupported intent type — rejected at schema validation
- Thin evidence available — packet returned with minimal items and no charge
- Invalid or missing required fields (address, intent) — request rejected
- Address outside covered jurisdictions — limited or no public records returned

## How this service works

Build one public-record packet for a homebuyer, land investor, developer, commercial tenant, or renovation profile. Renovation combines parcel facts, exact-subject permits, USDA basement and soil interpretations, sampled terrain, flood, wetlands, and county radon. Typed profiles control evidence and chargeability. No readiness, feasibility, condition, approval, value, occupancy, or closing verdict. Thin evidence is charge-free. npx @velinussage/locus-agent-skill add.

## Output

A structured JSON packet containing grouped follow-up items sourced from public records, a list of unanswered questions, handoff recommendations, a timeline of relevant events, and caveats about data coverage — all scoped to the confirmed transaction intent and address. If evidence is thin, the response is returned charge-free.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "intent": {
   "enum": [
    "homebuyer_due_diligence",
    "land_investor_due_diligence",
    "developer_predevelopment",
    "commercial_tenant_due_diligence",
    "renovation_planning"
   ],
   "type": "string"
  },
  "address": {
   "type": "string",
   "maxLength": 240,
   "minLength": 5
  },
  "statedUse": {
   "type": "string",
   "maxLength": 160,
   "minLength": 1
  },
  "projectType": {
   "type": "string",
   "maxLength": 160,
   "minLength": 1
  },
  "suiteOrUnit": {
   "type": "string",
   "maxLength": 80,
   "minLength": 1
  },
  "projectArchetype": {
   "enum": [
    "residential",
    "vacant_land",
    "multifamily",
    "retail",
    "restaurant",
    "office",
    "industrial",
    "logistics",
    "mixed_use",
    "other"
   ],
   "type": "string"
  },
  "transactionStage": {
   "enum": [
    "early_screen",
    "under_contract",
    "pre_closing",
    "pre_lease",
    "pre_application",
    "pre_construction"
   ],
   "type": "string"
  },
  "requestedAreaContext": {
   "type": "array",
   "items": {
    "enum": [
     "workplace_employment"
    ],
    "type": "string"
   },
   "maxItems": 1
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "kind": "transaction_follow_up",
  "state": "follow_up_items_found",
  "groups": [],
  "intent": "homebuyer_due_diligence",
  "caveats": [
   "Example artifact; not live data."
  ],
  "handoffs": [],
  "timeline": [],
  "followUpItems": [],
  "unansweredQuestions": []
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/locus-transaction-follow-up-packet-builder-e4035018/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)