Answers for teams building with Australian data.

Hoist Assets gives AI agents access to Australian business, asset, and regulatory data through one API.

PPSR and ABN checks are the first live-account datasets. The product direction is one governed integration for the Australian source data an agent needs.

No. Hoist Assets 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.

Hoist 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 asset checks before onboarding, ABN/GST checks before routing a workflow, and source-backed evidence for agent decisions.

Current public surfaces describe PPSR organisation and serial-number checks, ABN lookups, GST status, certificate metadata, counterparty evidence, and health endpoints.

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

Hoist is expanding toward more Australian business, asset, and regulatory datasets so teams can keep one integration point while the source catalogue grows.

The Data Sources page separates what is available now from what is planned for future release.

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 posture applies across surfaces: entitlement, 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 entitlement before live source traffic, higher limits, or paid usage are enabled.

API keys, OAuth permissions, source entitlements, 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.

Plans include API and MCP access. Usage pricing applies to live register checks, and live source traffic is enabled account by account.

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.

For public access requests, use Get API Access. Do not start from a public checkout link.