Shared by permission. Read with context.
See how agency records become public answers, what stays private and what the feed returns now.
Last updated:
From an agency record to a public answer
Sharing a listing is a decision by its representative. The same permission follows the record into every format.
The agency supplies the record
Manual entry, CSV import or a reviewed connector. Seller instructions and source references are recorded before wider sharing. A portal link alone is not permission.
Permission determines the fields
The audience, channel, purpose and expiry determine what can be returned. A withheld field stays undisclosed; it does not become a negative fact.
People and software read the same record
An authorised Open listing has a stable page and JSON, Markdown and JSON-LD representations. Checks show what was reported and what remains unknown.
Changes affect the next read
Withdrawal, expiry and changed permission are checked again. Integrators must remove unavailable copies and process removal notices, rather than treat an old response as permanent permission.
What the public feed returns now
This is a reading of the first feed page, up to 20 records. The demonstration contains fictional records, not live market inventory.
- Records on this feed page
- 6
- Read at
No next page was returned in this observation.
This observation measures a response, not market coverage, agency adoption, match success or data accuracy. Permission and availability can change after this read.
Inspect the public feedOpen does not mean everything
- Open listings
- Only currently authorised public fields appear in anonymous pages, feeds and public AI reads.
- Selected listings
- Professional discovery needs an eligible verified representative, their current matching buyer request and the seller’s restrictions. No anonymous results or counts.
- Off-market and drafts
- These are excluded from every implemented AI tool. Authorised human access has its own permission checks.
- Clients and documents
- Buyer requests use anonymous references. Client identities, contracts and financial documents stay with their chosen professionals.
Questions about sources and reuse
Can a portal listing be imported without agreement?
No. The source’s terms, distribution rights and agency authorisation must be established. Automated portal collection is not enabled. Rewriting a description does not supply those rights.
Is this an unrestricted open-data licence?
No. Access to a public record does not grant every reuse purpose. Check the record’s permissions and the agreed integration terms. Recheck before reuse.
Does a recorded check mean the property is verified?
No. Collected, validated with no issue, validated with an issue and unknown are separate states. The reporting role, date and permitted source provide context.
Does using RESO fields mean certified MLS access?
No. Local schema and sample validation are engineering checks. Formal certification and each MLS or data-source agreement remain separate.
Connect with a clear contract
Start with the public read tutorial. Real agency and CRM activation still require an agreed source, mapping and acceptance. Keep your CRM and client relationship.