Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
LJ Hooker website screenshot

LJ Hooker

LJ Hooker is one of the largest residential and commercial real estate brokerage and property management networks in Australia and New Zealand. Founded in Maroubra, Sydney in 1928, the franchise network reports 390 businesses and around 4,000 sales professionals, property managers and support staff, facilitated more than AUD$20 billion in property transactions during 2024, and manages roughly 100,000 properties valued at about AUD$82 billion on behalf of investors. It operates across residential sales and rentals (ljhooker.com.au), commercial (ljhcommercial.com.au), rural (ljhrural.com.au), land and projects (ljhland.com.au) and New Zealand (ljhooker.co.nz). LJ Hooker sits at the agency layer of the Australian property value chain — below the REA Group / Domain portal duopoly that distributes its listings, and upstream of PEXA electronic conveyancing and the PropTrack / CoreLogic valuation data concentration. Its API posture is honestly stated as none-published: there is no developer portal, no published API documentation, no API terms of use and no partner or data-feed programme on any LJ Hooker domain. The only programmatic surface located is an undocumented, vendor-operated website backend at api01.ljx.com.au, generated by OpenAPI Generator and consumed by the Agentpoint-built property search front end; that OpenAPI definition is not published. RESO — the Real Estate Standards Organization Web API and Data Dictionary — is a North American, NAR-driven regime with no Australian footprint, and LJ Hooker appears nowhere in the RESO certificates directory.

human only

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.

Kin Score

API Evangelist profiles LJ Hooker the way a machine reads it — 1 machine-readable artifact, 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 — LJ Hooker scores 15.9/100 (emerging), with a separate agent-readiness read of 0/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 Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 15.9/100 · emerging
Contract Quality 0.0 / 25
Developer Ergonomics 0.4 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Regulatory · Securities & Market Data 6.2 / 15
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile LJ Hooker

Each block below is one kind of artifact we hold for LJ Hooker. 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 1

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.

Lj Hooker Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for LJ Hooker — 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 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Access & Security 1

Authentication, authorization, and security posture

Learn 1

Tutorials, courses, talks, and written guidance

Operate 1

Status, limits, changes, and where to get help

Commercial 2

Pricing, plans, and the legal terms of use

← All providers · Data indexed from github.com/api-evangelist/lj-hooker · machine-readable index on apis.io