About

We index public records so wholesalers can move faster than the bigger software they used to pay for.

terminal.house is a small team building the lead source for the agentic era of real estate. We pull, score, and serve the motivated-seller signal — through an API, an MCP server, and a deliberately small web UI — so the operator with the best automation wins.

01 Why we exist

The lead-list industry stopped innovating. Wholesalers' tools didn't.

For fifteen years, every wholesaler in the country has paid a UI-first vendor a monthly fee, exported a CSV, and pasted it into something. The data is fine. The delivery is from another decade.

Meanwhile the operators who close the most deals are running GoHighLevel pipelines, Make.com flows, custom GPTs, and a Claude window with their full deal history loaded in. Their stack is agentic. Their lead source is a download button.

We exist to close that gap. Same county records. Same signals. Delivered as an API a person can curl, an MCP server an agent can call, and a webhook that fires the moment a parcel becomes a lead.

02 Why a focused start

The launch counties have the data, the volume, and the motivated-seller density to prove the model.

Our launch counties publish parcel, deed, lien, and code records online — most with usable JSON or scrapable HTML, not buried in a courthouse basement. The state business-entity registry exposes LLC managers, which means we can do something most lead-list vendors won't: unmask entity-owned parcels and surface the human behind the LLC.

Roughly half of US wholesale closings happen in the southern third of the country, with our launch geography leading on volume. We're starting where the data quality and operator demand line up, then expanding state by state. See the in-app coverage banner for current launch scope.

The bet

The next ten years of real-estate operations belong to operators with their own automation stacks — not to the platforms that try to lock them in.

Every part of terminal.house is built to be composable: the recipe DSL, the scoring formula, the MCP tools, the webhook payload schema. Take the data, run your stack, win deals. We're a lead source — not a CRM, not a dialer, not a coaching program. A primitive, not a platform.

Pillar · 01

Transparent, every pixel

The composite formula is published. Every signal has a source. Every score has a breakdown. If you can't argue with the math, you can't trust the lead.

Pillar · 02

Composable, by default

One recipe DSL drives the API, the MCP tools, the watchlists, and the CSV. Build the query once, run it everywhere. Swap any layer of the stack without losing it.

Pillar · 03

Honest about the boundary

We're not the CRM. We're not the dialer. We're not the skip-trace. We integrate with the tools wholesalers already trust — and we won't pretend to replace them.

Working at terminal.house

Small team, dev-native, distributed.

We are deliberately small. Founders write code. Code ships daily. We're hiring for one full-stack engineer and one data-ops lead, both remote. If you've shipped scrapers, run small infra, and have opinions about MCP — we want to talk.