Ray White
Ray White is Australasia's largest real estate group, a family-owned brokerage network founded in 1902 and headquartered in Brisbane, Australia, running 550+ Australian offices and roughly a thousand offices in total across Australia, New Zealand, Indonesia, Hong Kong, China, Papua New Guinea, the Middle East and Atlanta USA, spanning residential sales, auctions, commercial (Ray White Commercial / rwc.com.au), rural and livestock, property management, projects, marine, hotels, valuations, business sales, insurance and mortgage broking through sister brand Loan Market. In the Australian property value chain Ray White sits on the AGENCY side of a portal duopoly — it lists into REA Group's realestate.com.au and Domain rather than operating a portal or a registry of its own — and it is an API CONSUMER, not an API producer. In December 2025 Ray White named realestate.com.au and PropTrack its data partners explicitly for their "industry leading API architecture", piping that licensed market data into its proprietary OneSystem, NurtureCloud and Pulse platforms. Its API posture is therefore honestly stated as none-published — as of 2026-07-26 no developer portal, no public API documentation, no OpenAPI or OData $metadata contract, and no published partner-API application path could be found on raywhite.com or any developer/api/docs subdomain (all of which fail DNS resolution). RESO is absent — Ray White does not appear in the RESO certification directory, which is unsurprising because RESO is a North American, NAR-driven mandate with no Australian counterpart; Australia's closest thing to a required machine-readable property rail is PEXA electronic conveyancing, which Ray White transacts through as a participant rather than exposes.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Ray White the way a machine reads it — 2 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Ray White scores 18.7/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Ray White
Each block below is one kind of artifact we hold for Ray White. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Ray White — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 2
MCP servers, agent skills, and machine-readable catalogs
Build 2
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 6
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/ray-white · machine-readable index on apis.io