Answers for teams building with Australian data.

HoistAI powers AI agents with Australian data. Agents use it to search opportunities, check businesses and invoices, check assets, monitor records, flag red flags, and create Evidence Packs.

No. Finding opportunities is one HoistAI product. HoistAI also supports business checks, invoice checks, asset checks, monitoring, red flag review, licence checks, address checks, and Evidence Packs.

HoistAI can help check business and tax details on an invoice, such as ABN, GST status, business names, company records, and charity records where supported. It does not prove bank account control.

PPSR is a register commonly used to check whether personal property, such as vehicles, equipment, machinery, or other serial-numbered assets, has a registered security interest. In HoistAI, PPSR appears inside the human product "check an asset".

An Evidence Pack is a record of what was checked, when it was checked, what came back, and what needs review.

HoistAI can monitor supported opportunities, businesses, charities, assets, licences, and records for changes where account access and source coverage allow it.

HoistAI does not provide legal, financial, credit, tax, or compliance advice. It does not prove bank account control. It does not provide broad people-search products. Some source checks require approved account access.

Hoist Assets is the trading-name context for HoistAI Pty Ltd and some billing/legal surfaces. Public product copy now uses HoistAI for the Australian data platform.

No. HoistAI is operated by HoistAI Pty Ltd. Hoist connects to Australian source systems and returns structured results your software can use.

Hoist does not replace registry records, legal advice, lender policy, or human review where your workflow requires it.

HoistAI is for developers, agent builders, startups, internal AI teams, automation engineers, and platform teams that need Australian source data inside software workflows.

Common patterns include opportunity discovery, invoice checks before payment, asset checks before onboarding, monitoring, and Evidence Packs for agent decisions.

Current public surfaces describe opportunity search, ABR ABN/GST, ASIC company and business-name checks, ACNC charity status, PPSR organisation and serial-number checks, G-NAF address confidence, DFAT sanctions, ASIC professional/licence registers, certificate metadata, Evidence Packs, Due Diligence Records, audit-chain events, decision memory, and health endpoints.

Live source traffic is account-gated. Public docs and sample responses show the contract before paid source usage is enabled.

The Data page groups source coverage by human product labels and lists the technical sources underneath.

When a workflow lacks source coverage, Hoist should mark that boundary explicitly instead of guessing or implying a register result exists.

Hoist returns what the source says, with source and timing context wherever the endpoint supports it.

If a registry has stale or incorrect data, the correction path stays with that source. Hoist does not rewrite the source record.

No. The current PPSR posture is organisation and serial-number asset checks. Personal grantor search is outside the public Hoist Assets product boundary.

That boundary is intentional: agent workflows get useful source checks without widening into personal search flows.

No. Use REST when you own the application code, MCP when an AI host needs tools, and the CLI when you want repeatable terminal checks.

The same source access model applies across surfaces: access approval, authentication, and usage caps are enforced before live checks run.

Provisioned REST and CLI calls use Hoist Assets API keys. API calls send Authorization: Bearer <api_key>.

CLI calls pass the same API key with --token or HOIST_ASSETS_API_KEY.

MCP uses OAuth. A human approves the permissions an AI host can use before the host can call Hoist tools.

Account pages and logs are private-preview for provisioned accounts; public self-serve account management is not open yet.

Yes, where the host supports remote MCP connectors or local MCP server configuration.

Start with Integrations for host-specific paths, or read the MCP docs.

Yes. Hoist is built for teams that need Australian source data in production software and agent workflows.

Commercial usage still needs the right account access before live source traffic, higher limits, or paid usage are enabled.

API keys, OAuth permissions, source access rules, and usage caps limit what a client can call.

Provisioned accounts can review account activity through private-preview account surfaces. Public self-serve account management is not open yet.

There is no subscription and no prepaid credits. Public docs and API health checks are free; checks are metered pay-as-you-go in AUD with GST shown. ABN/GST checks are A$0.10 each and PPSR searches are A$2.75 each, GST inclusive.

See Pricing for the current plan posture and account-gated source access copy.

Approved accounts use the signed-in billing surface. Stripe handles cards and invoices; Hoist does not collect card numbers in custom forms.

To get an API key, sign up for an account. Do not start from a public checkout link.