CAIN-42 CAIN Studio

API reference · Trust Fabric

Check whether a recorded decision has been altered since it was written

GET /fabric/decisions/{decision_id}/integrity

Last reviewed 2026-10-02

GET /fabric/decisions/{decision_id}/integrity

Recompute the record's digest and compare it with the stored one.

Answers three distinct states rather than a boolean, because they mean different things to whoever is asking: intact=true the record is byte-for-byte what was written intact=false the row has been altered since it was recorded verifiable=false the record predates digests and cannot be checked

Tamper-EVIDENT, not tamper-proof: whoever can write the row can recompute the digest. Making that impossible requires a key this process does not hold or an append-only log outside this database, and neither exists yet.

Parameters

NameInTypeMeaning
decision_id requiredpathstring

Responses

StatusMeaningBody
200Successful ResponseJSON
422Validation ErrorHTTPValidationError
401No key, or a key that is not validJSON detail
429Rate limit for your plan reached; retry after the Retry-After secondsJSON detail

Try it

The request goes from your browser straight to this site. Your key is not stored unless you tick the box, and then only in this tab's session storage.

Code

curl -sS -X GET 'https://cainstudio.online/fabric/decisions/<decision_id>/integrity' \
  -H "X-API-Key: $CAIN_API_KEY"

Schemas used

HTTPValidationError · ValidationError

← Why this decision came out the way it did, and which run it belongs to · all 79 Trust Fabric calls · Tamper-evidence for one decision record →

Try CAIN-42 on your own agents

Create a free account and every new account starts with a 7-day trial of the full platform. Or try the sandbox first, with no account at all.

Create a free account →  ·  Try the sandbox  ·  See the whole ecosystem