Guide: field inspections

Prove that an inspection photo or video was captured on-site, on a real device, at the stated time — the same trust primitive as an insurance claim, in the inspection vocabulary. Read the Platform guide first for the shared model.

The sandbox seeds a neutral inspection case, VER-SANDBOX-INSPECTION, so you can explore without capturing anything.

1. List inspections

curl $PROVENANCE_API/v1/verifications \
  -H "Authorization: Bearer $PRV_KEY"

{
  "data": [
    { "claim_id": "VER-SANDBOX-INSPECTION", "overall_status": "verified", "overall_risk_score": 0 }
  ]
}

The identifier field is named claim_id on the wire because the schema is shared with the insurance surface. It holds whatever case identifier you submit.

2. Attest an inspection capture

curl $PROVENANCE_API/v1/verifications/attest \
  -H "Authorization: Bearer $PRV_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "bundle": { ...signed bundle... }, "case_type": "inspection" }'

{ "attestation_id": "…", "risk_score": 0, "status": "verified" }

3. Pull the provenance

curl $PROVENANCE_API/v1/verifications/VER-SANDBOX-INSPECTION/provenance \
  -H "Authorization: Bearer $PRV_KEY"

Each asset carries its device, cert-chain result, GPS, and risk factors — identical to the insurance surface. If you want to require a signal for inspections (say, on-site GPS), add a case_type-keyed risk-policy rule; no code change is needed.