API + MCP reference

Docs

terminal.house is the agent-native motivated-seller lead feed for Florida real estate. REST API, MCP server, outbound webhooks, CSV export — all driven by the same daily-fresh ingestion of county property records, code enforcement, lis pendens, and tax-collector data across Tri-County (Miami-Dade, Broward, Palm Beach).

New here? Start with the 90-second quickstart. If you already have a key, jump straight to the REST API reference or MCP setup.

What you can build

  • Wholesaling deal flow — query parcels matching motivated-seller signals (out-of- state owner, long tenure + high equity, active code violation, lis pendens, tax-delinquent, no-homestead, LLC-owned).
  • Pipeline automation — subscribe a webhook to a saved watchlist; new matches land in your CRM (GHL, Make.com, Zapier, custom) within seconds of the county source publishing.
  • Agent workflows — point Claude Desktop, Cursor, Windsurf, or your own agent at our MCP server. Tool calls like list_leads and get_lead are first-class.
  • Bulk back-fill — pull a CSV of every parcel in a county matching a recipe for one-off list-building (Operator tier and up).

60-second intro

Every authenticated request carries a bearer API key. Your first call hits GET /v1/leads with a saved recipe slug. Results count as lead-views against your monthly quota — re-fetching the same folio later the same UTC day is free.

first request
# Issue a key at terminal.house/api-keys, then:curl https://api.terminal.house/v1/leads?recipe=oos_long_tenure_high_signal&limit=5 \  -H "Authorization: Bearer th_live_d3a7...8c41"

The response is JSON: a paged results array, an opaque cursor, and the rate-limit + quota headers documented in Rate limits & quotas.

Surfaces

Where to next

  • 90-second quickstart — sign up, get a key, see a lead.
  • Authentication — key lifecycle, Bearer header, tier feature gating, MCP persistence.
  • Rate limits & quotas — per-tier caps, calendar-day idempotency, rate-limit headers, 429 / 402 behavior.
  • Errors — every status code, the JSON envelope, and the special cases (402, 423, 429, 5xx).
  • Changelog and versioning policy — what shipped recently, what's in v1's stability contract.