Integrations

Wire terminal.house into the tools you already use.

We're not your CRM. We're not your dialer. We're the lead source that pushes scored, signal-rich leads into whichever stack you already run on — in real time.

Wholesalers run terminal.house with

GoHighLevelZapierMake.comREsimpliSmarter ContactClaudeChatGPT

CRM · most-used

GoHighLevel

Land terminal.house leads as contacts in your acquisitions pipeline — pre-tagged, pre-scored, with the signal trace stored as custom fields. Trigger your existing GHL automations on the new contact.

Custom webhook — no marketplace install needed
Auto-tag th-hot for score ≥ 0.75
Pipeline + stage routing per recipe
Score, signals, deeplink as custom fields

ghl-mapping.json

// terminal.house → GHL contact mapping{  "endpoint": "https://services.leadconnectorhq.com/hooks/...",  "map": {    "firstName":           "{{owner.first_name}}",    "lastName":            "{{owner.last_name}}",    "address1":            "{{address.line1}}",    "city":                "{{address.city}}",    "customField.th_folio": "{{folio}}",    "customField.th_score": "{{score}}",    "customField.signals":  "{{signals_fired | join}}"  },  "tags":     ["th-hot", "motivated-seller"],  "pipeline": "acquisitions",  "stage":    "new-lead"}

Agentic · MCP standard

Claude · custom AI agents

terminal.house ships an MCP server at mcp.terminal.house. Drop the config into Claude Desktop or any agent client and your assistant can query leads, fetch parcels, and fire watchlists on your behalf.

Tools: leads.search, parcel.get, watchlist.fire, signal.explain
Bearer-auth with your API key — same key as REST
Composable: agent runs the recipe DSL natively
Counts toward Operator-tier lead-views, not a separate quota

~/.claude/mcp.json

{  "mcpServers": {    "terminal-house": {      "url": "https://mcp.terminal.house",      "transport": "http",      "headers": {        "Authorization": "Bearer th_live_..."      }    }  }} # test from claude:> find me 10 motivated parcels in 33125 with  out_of_state_owner + code_violation, score > 0.7

Raw API · zero glue

curl · any HTTP client

If your stack speaks HTTP, it speaks terminal.house. One bearer token, JSON in, JSON out. Same DSL the watchlist UI generates.

REST · cursor pagination · idempotent
Rate-limit headers on every response
HMAC-signed webhooks back to you
Open the docs · 90-second quickstart

terminal — bash

$ curl -X POST https://api.terminal.house/v1/leads/search \    -H "Authorization: Bearer th_live_..." \    -H "Content-Type: application/json" \    -d '{ "recipe": "oos_long_tenure_high_signal", "limit": 10 }' # 200 OK · 142ms · 4,853 lead-views remaining{  "results": [{ "folio": "30-3122-008-0440", "score": 0.78, ...}, ...],  "cursor": "eyJv...", "total": 340}