AUO is built entirely on free public government sources. That is a strength: it is transparent, attributable, and affordable. It also means there are things it deliberately does not do, because the data simply is not in the free public record. We state these plainly rather than paper over them.

​
What is not included

For an ordinary company, the current directors, shareholders, and beneficial owners are only available in the paid ASIC company extract, or not in any register at all. None of that is included. Every resolve response says so in its disclaimer.
This is a verification and monitoring layer. It confirms an entity exists, resolves it across registers, enriches it, and watches it for change. It is not a full Know Your Business or Customer Due Diligence workflow on its own.
Document Verification (DVS), Face Verification (FVS), and Director ID are the federally gated person-proofing layer that sits above this API. They are out of scope by design, not a gap.
Where bankruptcy signals are surfaced, they are petitions and applications (a pre-bankruptcy distress signal, an allegation), never an adjudicated “is bankrupt” status. The adjudicated register is paid and out of scope.

​
Where it fits

Think of it as the resolution, enrichment, and monitoring layer:
  • Below it: the raw government registers, joined so you do not have to.
  • This layer: resolve any Australian entity, enrich it with every free public source, and watch it for risk, with provenance on every field.
  • Above it: the paid, federally gated proofing layer (document and identity verification, Director ID) and the paid ASIC extracts (directors, ownership).

​
Why we publish this

Our closest competitors hide pricing and boundaries behind a “contact sales” wall. This one publishes everything: pricing, behavior, and limits. Knowing exactly what a tool can and cannot tell you is part of using it responsibly. That honesty is the point.

​
The disclaimer

Every resolve response carries a disclaimer field restating the ownership boundary, and every screen response carries one restating that no match is not a clearance. They are part of the response contract.

​
Next

Screening posture

Why screening is possible-match, never cleared.

The three surfaces

REST, MCP, and webhooks, and when to use each.