Response shape preview.

This page shows the JSON response your tool will parse against three sample organisations. The records below are sample data, rendered client-side - useful for shaping setup and demo flows, not for testing hashes, billing, or verification decisions.

What the response looks like Example shape

Account-gated searches return the official AFSA certificate URL when available, a signed Due Diligence Record, and a record_id for retrieval. The example shape uses <api-host> for the host your docs or dashboard provide.

{
  "record_id": "rec_01HX..",
  "search_type": "ppsr_search_organisation",
  "target": { "acn": "123 456 789", "name": "ACME Excavations Pty Ltd" },
  "certificate_url": "<api-host>/v1/certs/cert_01HX..pdf",
  "record_url": "<api-host>/v1/records/rec_01HX..pdf",
  "record_hash": "sha256:9f4e2c..",
  "audit_chain_id": "ac_2026-05-15-0042",
  "results": { "registrations": [ .. ] },
  "billed_at": "A$2.00 + A$0.50 workflow",
  "timestamp": "2026-05-15T03:42:11Z"
}

Call it from your tool

Use this page to validate parsing before calling Hoist from an AI client, CLI script, or API integration. MCP setup points at mcp.assets.hoistai.com/mcp; API and CLI calls use the API key and host shown in your docs or dashboard.

MCP (Claude Desktop, Cursor, Cline, ChatGPT, Gemini) Live

After installing (see /docs/mcp), ask your agent: "Run a PPSR organisation search on ACN 123 456 789 in sample mode." The agent calls the tool against sample data and returns the same JSON shape as the preview above.

curl against the REST API Setup example

Use your Hoist Assets API key and pass "sandbox": true while testing with sample data. No separate sandbox URL or auth model is required.

# Replace <api-host> with the host from your docs or dashboard.
curl https://<api-host>/v1/ppsr/search \
  -H "Authorization: Bearer $HOIST_ASSETS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"acn":"123 456 789","sandbox":true}'

Three sample data, predictable results

• ACME Excavations - three current registrations across two secured parties. Use this to see what a "loaded" PPSR record looks like.
• Totem Logistics - one historic, two current registrations, one expiring next month. Use this for renewal/expiry handling.
• Clean Slate - no registrations. Use this for "all clear" path testing.