Evidence records
Search certificates
Completed source checks produce audit-friendly records. PPSR searches can include source certificate metadata; due-diligence receipts summarize what ran, when it ran, which client called it, and the evidence fingerprints available to the account.
iHoist returns source-backed evidence and identifiers. It does not replace a legal review, credit decision, or tax advice.
What you get
| Record | What it proves | Where it appears |
|---|---|---|
| PPSR search certificate | The source certificate or certificate fingerprint for a completed PPSR search. | Search response and activity record when available. |
| Due-diligence receipt | A user-scoped register-search audit chain across PPSR and ABN checks. | GET /v1/receipts/due-diligence |
| Evidence Pack export | A generated PDF or exportable record for a source-backed evidence pack. | GET /v1/exports/{id} |
Receipt API
Use the due-diligence receipt endpoint to list recent authenticated source-check records for the user represented by the bearer credential.
GEThttps://api.assets.hoistai.com/v1/receipts/due-diligence
curl - due-diligence receipt
curl https://api.assets.hoistai.com/v1/receipts/due-diligence?limit=20 \
-H "Authorization: Bearer $HOIST_ASSETS_API_KEY"
Certificate fields
Display certificate data as evidence metadata, not as a raw source dump. The common fields are:
search_id- the search reference used to correlate activity.certificate_sha256- a fingerprint for a recorded source certificate.evidence_pack_id- the account-scoped evidence pack reference when present.completed_at- the timestamp for the completed source check.
MCP and console use
AI hosts can read receipts only when the user approves the receipt scope. The account activity page exposes the same search history and certificate indicators for human review.