Verifying the trust proof
Pull a self-contained proof that a job was done, done right, and billed honestly — and verify it without trusting us.
Every work order builds a tamper-evident record as it moves through its lifecycle. With the proof:read scope you can pull a self-contained proof package for any record:
curl "https://app.facilityopsiq.com/api/v1/records/WO-000188/proof" \
-H "Authorization: Bearer wo_your_key_here"What’s in the package
The package is designed to be verified offline, by anyone — it doesn’t ask you to trust FacilityOpsIQ. It contains: a snapshot of the record; the full hash-chain of lifecycle events; each event’s digital signature plus the public key to check it; per-event Merkle proofs to a batch root; and the external timestamp anchoring that root to an independent, public source.
Why it matters for integrations
When you push a completed job back into your PMS/ERP — or hand it to an insurer, a brand inspector, or a warranty claim — you can attach the proof package so the receiving system can confirm the record wasn’t altered after the fact. It’s the difference between "our system says it’s done" and "here’s independently verifiable evidence."
The deep-dive on how this works — and how it compares to a public blockchain — lives on the Trust Layer page.