Developers building AI agents that interact with Australian businesses often fall into a dangerous trap: assuming a valid checksum means a business is real. A new release of the AU Business Identity tool, version 0.2.0, directly addresses this by introducing live verification against the Australian Business Register (ABR). Previously, the tool only offered deterministic validation, checking if an Australian Business Number (ABN) or Australian Company Number (ACN) was structurally correct. Now, agents can confirm if a business is actually registered, active, and GST-compliant.

The Distinction Between Validation and Verification

The core update separates two distinct operations that were previously conflated in many developer workflows. The existing validate_abn tool remains local, deterministic, and lightweight, answering only if a number is structurally valid. The new verify_abn tool performs a network lookup against the live ABR. This returns rich data including entity name, type, status, GST registration, and location details. For an agent, the difference between "this number is formatted correctly" and "this business is active" is the difference between a successful invoice and a fraud alert.

Remote MCP Endpoint and Beta Access

The tool is deployed as a remote Model Context Protocol (MCP) server, eliminating the need for local installation or dependency management. The public endpoint is hosted at au-business-identity.auagentutilities.workers.dev/mcp. During the current public beta, no API key is required, lowering the barrier for developers to integrate this verification step into their agent workflows. The project is open-source and available on GitHub, while also being listed in the official MCP Registry under io.github.creatorhub121/au-business-identity.

Why This Matters for Builders

For developers building compliance, onboarding, or invoicing agents, the risk of acting on a "valid" but non-existent business is high. The creator of AU Business Identity deliberately kept validate_abn free of network calls to ensure deterministic behavior for offline checks. This architectural choice prevents agents from confusing a quick format check with a authoritative registry lookup. If you are handling Australian suppliers or customers, integrating this verification step is a low-effort, high-value safety net.

Key Takeaways

  • Version 0.2.0 introduces verify_abn for live registry checks alongside the existing validate_abn.
  • The tool is a remote MCP server requiring no local installation and currently no API key.
  • It distinguishes between structural validity (checksum) and operational reality (active registration).
  • The project is open-source on GitHub and listed in the official MCP Registry.

The Bottom Line

Stop letting your agents trust checksums blindly; this tool finally gives them the context they need to verify reality.