Solutions · real estate & proptech

The agent can list, reprice, offer and sign. Who allowed it?

Real-estate AI moved from drafting descriptions to taking actions: publishing listings, adjusting prices against the market, submitting offers, booking viewings, preparing tenancy agreements, and queueing deposit releases. Each one binds a seller, a buyer, a landlord or a tenant. KYE Protocol™ is the authority layer underneath your stack: every consequential action is admitted under a live, scoped mandate, the irreversible ones wait for a named person, and every binding act is sealed into evidence your compliance team — or a court — can re-verify later.

The governed actions

Six actions that bind someone — each with its own authority.

Below the line, your agents run at machine speed. Above it, the act stays provisional until a person with standing signs. You draw the line; the protocol enforces it.

Publish a listing

Wrong photos, wrong price, wrong disclosures — a bad listing is a live legal representation. The agent publishes only inside the mandate the office head approved. mandate-scoped · fast lane

Change a price

Within the agreed corridor, instant. Below the vendor's floor — held, routed to the named negotiator, and nothing moves until they act. corridor-bounded · escalates

Submit an offer

An offer commits your client. The agent prepares it; the buyer's recorded instruction and ceiling admit it; the evidence shows both, forever. client-instruction bound

Book viewings & chase

High volume, low consequence — exactly where agents should run free. Governed means the fast lane is provably fast, not just hopeful. fast lane · evidenced

Prepare a tenancy agreement

The agent assembles clauses from the approved library only. A novel clause is a reserved act — it waits for the person who may approve terms. approved-library only

Release a deposit

Irreversible and disputed more than any other act in the sector. Always above the line: a named person, checked for current authority, signs — and the seal proves it. named finality · always

Seeing is believing

The dashboard your branch managers actually open.

Real-estate leaders do not buy protocols; they buy the morning view: every agent action across every branch — what ran free, what was held, who signed, and the sealed evidence pack behind each. One screen answers the three questions that end disputes: was it in the mandate, who made it final, and can we prove it? The same view scales from a single office to a national brokerage network — the mandate is per branch, per negotiator, per vendor instruction, and the evidence rolls up without anyone compiling a spreadsheet.

Who this is for

Brokerages, portals, letting agents and the proptech that serves them.

The same authority spine, four different wedges.

Brokerage networks

Franchise-wide agent rollouts fail on trust, not technology. Per-branch mandates and named finality let head office grant autonomy it can defend — and revoke surgically.

Property portals

When third-party agents post through your platform, the bad listing lands on your brand. Per-action authority is the difference between hosting actions and answering for them.

Letting & property managers

Deposits, repairs above threshold, tenancy terms — the highest-dispute actions in the sector get named sign-off and a replayable record by default.

Proptech builders

"Our agent cannot exceed its mandate, and here is the proof" closes enterprise deals that capability demos cannot. Ship the authority layer inside your product.

Start where every engagement starts: the tailored authority diagram of your own stack, then a scoped pilot on your highest-dispute action class.