Skip to content
↑↓ to move · Enter to openEsc to close
Example verification flowScenario 05

AI agents in real estate: verifying the buyer's agent before a showing

Mike wants to see a house and read the disclosures before he does. His buyer's brokerage runs an agent that contacts the listing brokerage's agent: "I'm requesting a showing for my buyer." The listing side is about to put a stranger on a seller's calendar and send documents about the property.

This scenario shows how a listing brokerage can check which agent is asking, and which brokerage stands behind it, before anything is released.

Ready
Human
Mike
“Book a showing at 14 Alder Lane and get the disclosures.”
Buyer’s agent
Identity proof
Crestline buyer agent
Operator: Crestline Realty · representing Mike
“I’m requesting a showing for my buyer.”
Listing brokerage agent
Maple & Stone Realty
Showings and disclosures agent
Who are you?
Example verification flow
Fresh challengenonce 61D0·B7
Proof of control✓ VALID
Operator declarationL1_REGISTEREDDECLARED
Domain claimL2_DOMAIN_VERIFIED✓ VERIFIED
StatusACTIVE
Checked separately
Disclosure packageBROKERAGE POLICY

Identity is not permission. Knowing which buyer’s agent is asking does not open the property or the file — the seller’s instructions and the brokerage’s policy decide what is released, and to whom.

Awaiting proof
Nothing proceeds on an unproven claim
What AgenID proves here

Which agent requested the showing and who declared it, with its brokerage’s domain claim independently verified. Property access, disclosure release and any offer remain decisions for the seller and the brokerages.

Illustration, not deployment

These scenarios illustrate the protocol's verification model. The reference deployment at agenid.com issues nothing above L1_REGISTERED today: L2 and higher require a VerificationAssertion signed by a root authority key, and that key has not been created. L5 is reserved by the spec and is not issuable at all.

Challenge–response is a proposed interaction pattern. v1.1.1 defines the signed objects, not this exchange.

Why showing requests are a trust decision

A showing puts someone inside a seller's home, and a disclosure package contains details the seller shared for serious buyers. Listing agents already screen callers by phone and email, and both are easy to imitate. As buyers' brokerages automate scheduling, the listing side needs a way to tell a real brokerage's agent from an agent claiming to be one.

How the listing brokerage checks the buyer's agent

The buyer's agent presents its AgenID. The listing brokerage's agent resolves it and re-verifies the operator's signature on the manifest, which names the brokerage that runs the agent. The operator declaration shows as DECLARED at L1_REGISTERED; the illustration then shows L2_DOMAIN_VERIFIED, meaning an authority checked that the operator controls the domain it names.

Because the identity is persistent, the listing side can see that the same agent later asks for a second showing or submits an offer, rather than treating every message as a new unknown.

Access and disclosures stay with the seller's side

Identity does not open a door or a file. What is released, to whom and when follows the seller's instructions and the listing brokerage's policy. Offers, representation and everything a transaction requires remain with the parties and their brokerages.

Today the reference registry at agenid.com issues DECLARED and L1_REGISTERED. The higher levels shown in this illustration require an assertion signed by a root authority key that has not been created yet, so they describe how the protocol works rather than something you can obtain today.

Frequently asked questions

Can an AI agent schedule a property showing?

Many scheduling tools already do. What they usually cannot tell the listing side is which agent is asking and which brokerage stands behind it. A portable identity makes that checkable.

How does a listing brokerage verify an AI agent?

It resolves the agent's AgenID, re-verifies the operator's signature on the manifest, and checks which claims about the operator, such as control of its domain, have been independently verified.

Does verification entitle the agent to the disclosure package?

No. AgenID answers which agent is acting and who declared it. What that agent is allowed to do stays with the business on the other side and with the operator that runs the agent. Protocol v1.1.1 defines no signed authorization object.

Does the listing brokerage need an account with AgenID?

No. Resolution is a public HTTPS request, and the signature check uses standard Ed25519 verification over RFC 8785 canonical JSON. No adapter package is published yet for any real estate platform.

Integration patterns for this scenario

How the identity travels through platforms agents in this scenario commonly run on. Each brief is a pattern using the platform’s documented APIs, not a shipped adapter package.

Give your agent an identity

Register an agent in the browser — the signing key is generated on your device and never sent to AgenID — or resolve an existing AgenID and re-check its signature yourself.