VaultRE
VaultRE - now marketed as MRI Vault CRM, after VaultRE's parent Vault Group / PropTech Group was absorbed into MRI Software - is an Australian cloud real estate CRM and transaction platform used by residential, commercial, rural, land, business and property-management agencies across Australia and New Zealand. It sits in the agency and CRM layer of the value chain rather than the portal or registry layer: it holds the agency's contacts, appraisals, listings, offers, open homes, feedback, tenancies, maintenance, invoicing and AML records, and feeds listings outward to Australia's portal duopoly (realestate.com.au and Domain) instead of being a portal, a land registry or a conveyancing rail itself. Unlike most of this sector, VaultRE publishes a genuinely open, versioned, machine-readable contract - a public MkDocs developer site at docs.api.vaultre.com.au carrying downloadable OpenAPI 3.0.1 documents for v1.1, v1.2 and v1.3 of the core API (324 paths and 453 operations in v1.3) plus a separate Aggregator API for franchise-group CRM data feeds. The API surface is documented openly but access is not self-serve: anyone can read the docs and download the specs, but API keys are issued only after an integrator-registration request is reviewed and approved (VaultRE states new integrations are generally created within two business days), and each agency must then mint a scoped access token for that integrator from inside its own VaultRE account. RESO plays no part here - Australia has no RESO mandate and no RESO, OData or $metadata reference appears anywhere in VaultRE's documentation or specifications; the local listing-distribution seam is REAXML and portal-specific feeds instead. Auth is a static X-Api-Key integrator key paired with a per-account Bearer access token, with an OAuth2-style authorisation-code flow available for token minting, scoped tokens readable via GET /scopes, HMAC-SHA512-signed webhooks, and published rate limits of 10 requests per second and 10,000 requests per day.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles VaultRE the way a machine reads it — 59 machine-readable artifacts across 4 APIs, 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 — VaultRE scores 49.9/100 (developing), with a separate agent-readiness read of 33/100 (agent ready). 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. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.
Kin Score
How this is scored →scored 2026-09-08 · rubric v0.20.0
Put this on your own site. The badge is drawn live from VaultRE's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/vaultre/"
title="VaultRE on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/vaultre.svg"
alt="VaultRE Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/vaultre/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/vaultre/"
title="VaultRE on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/vaultre/card.svg"
alt="VaultRE Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile VaultRE
Each block below is one kind of artifact we hold for VaultRE. 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.
APIs 50
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
VaultRE Advertising API
Operations related to property and agent advertising
VaultRE Aml API
Operations related to AML checks
VaultRE Buildings API
Operations related to buildings
VaultRE Bulk API
Bulk operations
VaultRE Business Properties API
Operations related to business properties
VaultRE Calendar API
Operations related to calendar events
VaultRE Campaigns API
Operations related to marketing campaigns
VaultRE Categories API
Operations related to categories
VaultRE Clearing Sales Properties API
Operations related to clearing sales properties
VaultRE Commercial Properties API
Operations related to commercial properties
VaultRE Conjunctionals API
Operations related to conjunctional property deals
VaultRE Contacts API
Operations related to contacts
VaultRE Corelogic API
Operations related to CoreLogic
VaultRE Deals API
Operations related to commercial deals
VaultRE Email API
Operations related to email
VaultRE Enquiries API
Operations related to listing enquiries
VaultRE Event Stream API
Operations related to the event stream
VaultRE Feedback API
Operations related to property feedback
VaultRE Fmsleads API
Operations related to FMS leads
VaultRE Holiday Rental Properties API
Operations related to holiday rental properties
VaultRE Inspections API
Operations related to inspections
VaultRE Integrator API
Special endpoints for access by integrating partners
VaultRE Invoices API
Operations related to invoices
VaultRE Keys API
Operations related to property keys
VaultRE Land Properties API
Operations related to land properties
VaultRE Lists API
Operations related to distribution lists
VaultRE Livestock Properties API
Operations related to livestock properties
VaultRE Maintenance API
Operations related to maintenance jobs
VaultRE Merge Fields API
Operations related to merge fields for SMS and email templates
VaultRE Messages API
Operations related to franchise and user messages
VaultRE Openhomes API
Operations related to open homes
VaultRE Precincts API
Operations related to precincts
VaultRE Properties API
Operations related to properties
VaultRE Property Offer API
Operations related to property offers
VaultRE Property Offer Conditions API
Operations related to property offer conditions
VaultRE Property Stats API
Operations related to property portal stats
VaultRE Reinz API
Operations related to REINZ
VaultRE Residential Properties API
Operations related to residential properties
VaultRE Rural Properties API
Operations related to rural properties
VaultRE Search API
Operations related to performing searches
VaultRE Sms API
Operations related to SMS
VaultRE Staff API
Operations related to staff
VaultRE Suburbs API
Operations related to suburbs
VaultRE Suggest API
Operations related to suggest services
VaultRE Suppliers API
Operations related to creditors / suppliers
VaultRE Tasks API
Operations related to tasks
VaultRE Templates API
Operations related to SMS and email templates
VaultRE Tenancies API
The tenancies API from VaultRE — 1 operation(s) for tenancies.
VaultRE Types API
Operations related to various VaultRE object types
VaultRE User API
Operations related to users
Scroll within the panel for all 50 ·
Open Collections 4
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
VaultRE Aggregator
OPEN COLLECTIONVaultRE
OPEN COLLECTIONVaultRE
OPEN COLLECTIONVaultRE
OPEN COLLECTIONEvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Vaultre Webhooks
ASYNCAPISecurity 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.
Scopes 1
OAuth scopes are the vocabulary of least-privilege access. Profiling them shows exactly what an integration — or an agent acting on a user's behalf — is allowed to do.
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for VaultRE — 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.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 5
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 5
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/vaultre · machine-readable index on apis.io
This is an independent, third-party profile of VaultRE, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.