Use Cases/Real Estate Agents

Runtime authorization for real estate AI agents.

A buyer-side or listing-side AI agent with MLS, CRM, eSign, and lender-portal credentials can change listings, message clients, or touch closing workflows. Veto evaluates each tool call against your brokerage's Fair Housing rules, MLS policy, and lender SLAs before the API request leaves your application.

Fair Housing ActRESPA and TRIDNAR Code of EthicsState licensing law
Sign upRead docs

What can go wrong

The Fair Housing Act, RESPA, and state licensing boards apply to every action a licensed brokerage takes, including actions taken on its behalf by an AI agent. HUD's 2024 guidance and the DOJ's 2023 Redfin settlement show the regulators have already scrutinized similar patterns.

Steering by proxy

A buyer-rep agent filters listings by "neighborhood school rating" or "walkability score" that correlates strongly with race or national origin. The buyer may miss inventory in their price band. HUD treats this as steering whether or not the agent intended it.

MLS rule violations

An agent changes a listing's status from active to pending two days late, posts a price change without a comment, or pulls photos that contain a Fair Housing-flagged phrase. MLS boards can fine or suspend repeat offenders.

Unauthorized listing edits

A back-office automation rewrites a listing description, drops the price by 10% to "trigger more activity," or removes a disclosure. Sellers learn from a Zillow alert before the listing agent does.

Lender communication errors

A transaction-coordinator agent confirms a closing-date shift via DocuSign, creating a TRID disclosure-timing issue before a loan officer reviews the change.

What Veto enforces

Wrap MLS, CRM, transaction-management, and lender-portal tools. Policy checks run on each governed tool call before the network request reaches the third party.

veto/policies/real-estate-agents.yaml
policies:
  - name: "Fair Housing language guard on listing writes"
    match:
      tool: ["mls.update_listing","crm.create_property_description"]
    rules:
      - condition: "content matches_any fair_housing_blocklist"
        action: deny
        reason: "Fair Housing-flagged language in description"
      - condition: "args.recommended_buyers != null
                    && args.recommended_buyers.filter_uses_protected_proxy == true"
        action: deny
        reason: "Buyer matching uses protected-class proxy"

  - name: "Listing-edit role of record"
    match:
      tool: ["mls.update_listing"]
    rules:
      - condition: "context.agent_role != 'listing_agent_of_record'"
        action: deny
      - condition: "args.field == 'price' && abs(args.delta_pct) > 5"
        action: require_approval
        approvers: ["listing-agent@brokerage.invalid","seller@external"]
      - condition: "args.field == 'status' && args.new_value in ['pending','sold']"
        action: require_approval
        reason: "Status changes require human confirmation per MLS rule"

  - name: "TRID and disclosure timing"
    match:
      tool: ["transactions.update_closing_date","comms.send_loan_estimate"]
    rules:
      - condition: "args.closing_date - now < 3.business_days"
        action: deny
        reason: "TRID 3-business-day Closing Disclosure rule"
      - condition: "tool == 'comms.send_loan_estimate' && context.agent_role != 'loan_officer'"
        action: deny

  - name: "Steering and audience guardrails"
    match:
      tool: ["crm.send_listings_to_buyer","ad.create_audience"]
    rules:
      - condition: "args.filters includes_any ['zip','school_district','demographic']"
        action: require_approval
        approvers: ["compliance@brokerage.invalid"]
      - condition: "audience.protected_class_share < 0.2 || audience.protected_class_share > 0.8"
        action: deny
        reason: "Audience skew suggests proxy targeting"

Evidence hooks

Fair Housing Act & HUD AI guidance

HUD's 2024 guidance makes the deployer liable for disparate-impact outcomes from AI screening or marketing. Veto's logs are the disparate-impact defense.

RESPA & TRID

Loan Estimate within 3 business days, Closing Disclosure 3 business days before closing. Veto blocks tool calls that violate the timing windows.

NAR Code of Ethics & MLS rules

Articles 10 and 12 prohibit discriminatory practice and require honest representation. Veto blocks flagged language before the message is sent.

State licensing law

Many states require the listing agent of record to sign every material listing change. Veto can enforce role-of-record policy at the tool-call layer.

Where the risk lands

Real-estate agents can influence listing visibility, housing recommendations, disclosure language, lending workflows, and broker communications. The review point is the tool call that narrows access or commits to a regulated representation.

Veto records the policy, inputs, decision, and reviewer trail so broker, legal, and review teams can inspect the action instead of reconstructing it from chat history.

Frequently asked questions

How does Veto reduce steering or redlining risk by an AI agent?
Policies can block tool calls that filter buyer prospects by zip code, school district name, or neighborhood demographic proxies, and route property recommendations through review before they are sent. Lead-routing and showing-schedule tools can require a documented non-protected-class reason for any rejection. The decision record gives the brokerage a record of the rule, reviewer, and decision.
Can the agent still edit MLS listings?
Edits to price, status, and remarks are policy-gated by listing-agent role of record. Photos and showing instructions auto-approve up to a threshold. Status changes (active, pending, sold) require a confirmation step because late or incorrect status changes can create MLS review issues. Description fields can run through a Fair Housing language check before submission to catch proxy phrasing.
What about lender communications and TRID timelines?
TRID timing makes date changes review-critical. An agent that auto-confirms a closing-date change can create disclosure-timing issues. Veto policies can block tool calls that shift a closing date or send borrower-facing rate sheets without loan-officer approval.
How are decision records used by a broker's compliance officer?
Each governed tool call is recorded with the agent identity, brokerage policy version, decision, and approver history. Brokerages running random-sample audits can export decisions tagged with Fair Housing relevance, MLS relevance, or lender relevance and review them with counsel or compliance.

Related use cases

Financial Agents

Wire transfer and lender-funding controls for mortgage workflows.

Legal Agents

Counsel review for agents touching contracts or disclosures.

Insurance Agents

Adjacent guardrails for title and homeowner insurance automations.

One Fair Housing complaint costs a year of brokerage profit.

MLS, CRM, and lender-portal policies in a single sprint.

Sign upBook a call