destill.ai · All sectors · Deutsch · Trust Center
For credit risk, internal audit and model risk teams
An agent declines a loan. The customer objects. Where is the proof?
When the supervisor or the customer asks, today you often have logs that someone with database access could change. Proof of Agent Work turns each step of your credit agent into a signed receipt that your audit team, and the supervisor, can check without us.
Try it yourselfRequest a pilot
Internal audit
Logs in a tool the business unit administers are a statement, not evidence. Audit wants to check the trail independently.
Model risk
Which model in which version made the score? Six months later, nobody wants to reconstruct it from tickets.
Customer complaints
An explanation of a decline needs the decision path as it was, not as it was later rebuilt.
The film
The opening scene, as a short clip.
The full explainer
Chapters
Try it yourself: a signed receipt you can check
This is the kind of receipt you would get from every run of your agent after the pilot. Synthetic data, real cryptography: an ML-DSA-65 signature and an RFC 3161 time stamp from an independent authority. Check it in your browser, then check a copy where one value in step 3 was changed.
Credit decision by an AI credit agent (fictional applicant)
| Step | What the agent did | Time (UTC) |
|---|---|---|
| 1 | Application receivedapplicationId: APP-2026-01187 · product: consumer loan · amountEUR: 18000 · termMonths: 60 · documents: 2 × hash | 08:02:11 |
| 2 | Credit bureau report retrievedsource: credit bureau · report: hash | 08:02:13 |
| 3 | Score computedmodel: credit-scorer 2.4 · score: 612 · cutoff: 640 | 08:02:14 |
| 4 | Affordability checkeddebtToIncome: 0.41 · limit: 0.4 · result: above limit | 08:02:14 |
| 5 | Decision proposeddecision: decline · reasons: score below cutoff, debt-to-income above limit | 08:02:15 |
| 6 | Human reviewrole: credit officer · reviewer: hash · outcome: decline confirmed | 09:40:02 |
| 7 | Customer notifiedchannel: letter · explanationOffered: true · letter: hash | 09:40:05 |
Check this receiptCheck a tampered copy
Download the receipt (JSON) · Or drag the downloaded file into the verifier yourself, edit one number in a text editor, and drag it in again.
Your engineers can repeat the check offline with OpenSSL 3.5 or later and the published script: check pack.
What you get
Each item carries its status from our feature register: Built, Pilot or Roadmap. Hover a label for the evidence behind it.
One signed receipt per agent run: every step, in order, with model and version. Post-quantum signature ML-DSA-65 (FIPS 204). Time stamp from an independent RFC 3161 authority; nobody can backdate the receipt, us included. Fortress TRACE: one invisibly marked copy per recipient; if a copy turns up, you see whom it was sent to. The human approval signed with the reviewer’s own key. Append-only transparency log with inclusion proofs. Keys in hardware (HSM).
The legal frame
Where a receipt helps you evidence an obligation. It does not fulfil the obligation for you and does not make anyone conform with the law by itself. Not legal advice.
AI Act, Annex III no. 5(b) with Art. 12, 19 and 26(6)
Credit scoring of natural persons is high-risk; such systems must log events automatically, and providers and deployers keep the logs for at least six months. Since the Digital Omnibus these duties apply from 2 Dec 2027. A receipt helps you evidence that the log existed at a fixed time and was not changed since.
Source: eur-lex.europa.eu
Consumer Credit Directive (EU) 2023/2225, Art. 18(8)
With automated creditworthiness assessment the consumer may ask for human intervention, an explanation and a review. The receipt helps you evidence that and when a person reviewed the decision; the assessment itself stays with you.
Source: eur-lex.europa.eu
GDPR Art. 22(3) and 15(1)(h)
Right to contest an automated decision and to meaningful information about the logic involved. The signed trail helps you answer with the steps that actually ran.
Source: eur-lex.europa.eu
DORA Art. 17, 19 and 28
ICT incident process and reporting: a time-stamped trail helps you evidence the timeline of an incident. Third-party risk: if the receipt service runs in your data centre, we are not your ICT provider for it; if you use our hosted service, we are one, and we answer your provider questionnaire in the pilot.
Source: eur-lex.europa.eu
eIDAS and ETSI TS 119 461 (remote identity proofing)
If you onboard customers remotely, ETSI TS 119 461 sets the requirements for identity proofing, including protection against injected video. We claim no conformity: Fortress SEAL is not a certified identity-proofing component, and device attestation is still in development. A receipt can document which onboarding steps ran.
Source: www.etsi.org
The honest limit
A receipt proves who signed which steps, and when. It does not prove that the agent was right, and it does not prove that nothing was left out: it covers what was logged. The SEAL shows a change made after capture; it never says a picture is "not AI-generated". Keys are held in software today; hardware custody is on the roadmap.
The pilot: 8 weeks, price after scoping
Scope
One agent workflow, for example a credit decision or a service-provider process under DORA. POAW complements your existing trace tools (for example Langfuse or LangSmith): one receipt per trace section. Runs in your data centre: the receipt service is a Docker project with its own Postgres database, its setup is written down step by step and has been run end to end from nothing; you create your own signing keys, which never reach us. If a core-banking or platform provider runs the agent for you, the pilot can start there; we are looking for such providers as integration partners. Final report with go/no-go.
Price frame: The pilot has a fixed price, agreed after scoping. After a successful pilot: an annual licence, scaled by volume. Amounts only in the written offer. Contracting party: destill.ai Ltd. (Cyprus, in formation). Until it is registered, Lebensfluss e.V. (Austria, see footer) signs the pilot.
Success criteria, agreed in writing at kick-off
- At least 99 % of AI steps in the pilot workflow produce a verifiable receipt.
- Your team verifies a receipt on its own, without our help (OpenSSL).
- Extra effort per work step is measured; we set the target together at kick-off.
Source: our written pilot offer; the targets are what we commit to measure, not results from an earlier pilot.
What you provide
- One concrete workflow and an owner
- Test data or test images and access to a test environment
- Contacts from IT and compliance or audit
- Internet access when signing (for the time stamp)
- Your own legal assessment
- Connection to your agent or trace tools
Want the written pilot offer? Choose "Talk about a pilot" below and we send it with our reply.