Fictional demonstration. No real properties, clients or agencies.

Trust and custody

# The seller decides who sees the listing.

An agent records the seller’s permission before sharing a listing more widely.

Last updated: 30 September 2026

## Three choices for sharing a listing.

The seller’s recorded instruction controls exposure. An agent cannot make a listing more public just by changing a label.

- Public · Open:

Anyone can read an authorised public record, including search engines and AI assistants.

The page, Markdown, JSON, public feed and public search use the same publication rules. Permission to crawl does not guarantee indexing or an AI recommendation.

- Conditional · Semi-open:

Only an authenticated, eligible professional with a valid represented buyer request can discover a matching record.

The server checks the buyer context and the seller’s criteria. These listings do not appear in public search, feeds, sitemaps or anonymous AI tools.

- Exclusive · Off-market:

Authorised human professionals use the protected workbench under the seller’s instructions.

These records are excluded from LLM-facing search, AI tools and public publishing.

Draft is preparation, not an exposure tier. Only the listing agency can see it; it is excluded from public and AI access.

## Know what the network holds.

### Information used for matching

Property details, rights-attested listing photos, anonymous buyer criteria, seller instructions, professional account information and attributed check status are stored by Speaking Bricks.

### Documents remain with their holder

Client names and contact details, identity files, bank statements, contracts and inspection reports do not belong in the listing or buyer-request database. A check records its status, reporting role, date and an opaque reference to its source.

## A check is an attributed report.

A licence review, seller instruction and technical check answer different questions. The record identifies what was reported and its source; an unknown check stays unknown. Fictional verification is labelled as fictional, not presented as a real agency licence or property inspection.

## Permission can change.

Wider sharing needs a current seller instruction and distribution rights. Revocation or withdrawal removes access through the live service. Integrators must re-check permission and remove unavailable copies; Speaking Bricks cannot erase a copy already held by an independent service.

## Standards and real-world permissions

Speaking Bricks is not RESO-certified. Its JSON, OpenAPI and MCP interfaces are custom interfaces, not a certified RESO Web API. Interoperability needs an agreed field mapping and conformance testing.

There is no active MLS/IDX data-feed agreement in this demonstration. A future network or CRM agreement must cover the intended use, including AI access, redistribution and removal. Real operation also requires reviewed privacy notices, professional eligibility rules and competition-law governance.

[What RESO certification covers](<https://www.reso.org/certification/>)

[Current demonstration legal notices](<https://speakingbricks.eu/legal/privacy>)

For AI and developers
- [AI directory (llms.txt)](<https://speakingbricks.eu/llms.txt>)
- [Open listings (JSON)](<https://speakingbricks.eu/feeds/open-listings.json>)
- [Developers](<https://speakingbricks.eu/developers>)

[HTML](<https://speakingbricks.eu/trust?lang=en>)