Australian data for integrators building AI agents.
Connect your agent to Australian source data without building the register plumbing yourself. Hoist checks enabled sources and returns an Evidence Pack with timestamps, risk flags, and review notes through API, CLI, or MCP.
What your agent can ask Hoist
- "Can this vehicle and ABN be checked together?"
- "Is this invoice counterparty registered and unencumbered?"
- "Does this asset have a PPSR registration against it?"
- "What changed since we last checked this counterparty?"
- "Is this business entity GST-registered at the stated ABN?"
An Evidence Pack containing: result, source checks, timestamps, source references where applicable, risk flags, confidence, and review items. The Evidence Pack is the full agent-facing result your agent consumes.
Three access surfaces
| Surface | When to use | Status |
|---|---|---|
REST APIapi.assets.hoistai.com/v1/ | Apps, backends, custom agents, and automation tools. | Account access |
CLInpx @hoist-assets/cli | Shell scripts, local checks, and repeatable terminal checks. | Account access |
MCPmcp.assets.hoistai.com/mcp | Agent hosts that support MCP. PPSR and ABN checks require account access. | Account access |
Hoist Assets sets up API, CLI, and MCP access directly. Source checks depend on account setup, source availability, and confirmation before paid calls run.
A day, before and after account access
Build register connections, access limits, audit logs, and price confirmation yourself.
With account access, connect Hoist through API, CLI, or MCP. Access limits, Evidence Pack schema, and price confirmation are built in. Your agent asks the question. Hoist returns the source-backed answer.
Agent runs Hoist can support
One config snippet, source-backed answers
With account access, connect through API, CLI, or MCP. Your agent can run PPSR searches and verify ABNs on demand, with paid-call confirmation and Evidence Packs returned in structured JSON.
Counterparty risk agent
With account access, build an agent that calls abn_lookup, then ppsr_search_organisation, then summarises the Evidence Pack. Calls are bounded by the account's access settings and paid-call confirmation policy.
Paid calls stay explicit
With account access, use the API for applications that need repeatable source checks. Your platform forwards the Evidence Pack to your user. Billing rules are set during account setup.
Current surface
- REST API:
api.assets.hoistai.com/v1/with account access. - CLI:
npx @hoist-assets/cliwith account access. - MCP endpoint:
mcp.assets.hoistai.com/mcpwith account access. - PPSR and ABN source checks require source availability and paid-call confirmation.
- Sample Evidence Pack responses are available from the public sandbox page.
Supported hosts
Hoist is designed for MCP-compatible hosts, custom agents, backend services, and terminal checks. Custom agents connect via API, CLI, or MCP when supported by their runtime.
* Your AI tool of choice: Hoist is model-agnostic. It works through MCP, API, and CLI. Host availability depends on the AI tool or agent runtime. See the Connector docs for the current host guide list.
Pricing
Pricing depends on account access, enabled datasets, and expected volume. Paid source checks require confirmation before they run. See /pricing for the current public plan shape.
FAQ
01Can we connect through API, CLI, or MCP?
Yes. Hoist exposes a REST API for apps and backends, a CLI for terminal checks, and an MCP endpoint for agent hosts that support MCP. Live source checks require account access.
02What does an Evidence Pack contain?
An Evidence Pack is the structured answer Hoist returns to your agent: result, source checks, timestamps, source references where applicable, risk flags, confidence, and review items.
Other use cases
Preview the response shape.
Sample responses show the Evidence Pack shape. API, CLI, MCP, and billing access are set up by account. Ask for API access if you want Hoist in your agent run.