VERIFIABLE AI INFERENCE LOGGING
When your AI gets it wrong, can you prove what happened?
AI Logger creates a tamper-evident record of every inference made through your wrapped OpenAI or Anthropic client. Reconstruct what your application sent, what the model returned and when it happened, then generate a report whose integrity anyone can check.
Plaintext input and output are protected inside your application before anything is transmitted.
The difficult question arrives after the output
A customer disputes an answer. An automated workflow takes the wrong path. A reviewer asks which model handled the request. Engineering can usually find fragments across provider dashboards, application logs and screenshots. The harder task is showing a complete record that has not been changed after the event.
- What did the application send?
- What did the model return?
- Which system handled the call and when?
- Can anyone with access alter the record?
- Can someone outside your team verify it?
If any answer is not sure, your audit trail has a gap.
AI capability is moving faster than accountability
- 362 documented AI incidents were recorded in 2025, up from 233 in 2024. Source Stanford AI Index 2026 (opens in a new tab).
- AI agents still fail roughly one in three attempts on structured computer-use benchmarks. Source Stanford AI Index 2026 (opens in a new tab).
- OWASP (opens in a new tab) recommends audit trails for AI agent compliance and forensics, including records of decisions, tool calls and outcomes.
AI Logger provides the captured inference record. Wider agent actions and calls outside the wrapped client require additional instrumentation.
A verifiable record from application to report
Step 1: Wrap the client
Add AI Logger to a supported OpenAI or Anthropic client and use the wrapped instance for model calls.
Step 2: Capture the inference
AI Logger creates a structured record of the input output and associated metadata for each captured call.
Step 3: Protect the record
Input and output are hashed with SHA-3 and encrypted with AES-256-GCM inside the application. The backend stores hashes and ciphertext rather than plaintext.
Step 4: Verify and report
Integritas anchors proof of the record on Minima. Generate a PDF report with inference entries and a receipt that can be checked independently.
Evidence should not depend on trust in the database
Ordinary logs are useful for operations, but administrators may be able to edit or delete them. AI Logger hashes each captured record and anchors proof independently. If the evidence changes later, the verification no longer matches.
- Encrypted at source
- Structured inference records
- Independent integrity check
- Verifiable PDF reports
The proof shows that a captured record has not changed. It does not prove that calls made outside the integration were captured.
Built for the moment someone asks for evidence
Incident review
Reconstruct the captured inference at the centre of a complaint error or unexpected outcome.
Customer assurance
Show enterprise customers how production AI calls are recorded protected and verified.
Internal governance
Connect AI policies and approvals to evidence from the system that actually ran.
Audit readiness
Generate a report that helps reviewers inspect captured activity without relying on a screenshot.
Regulatory preparation
Support record-keeping and traceability work while your legal and governance teams assess the obligations that apply.
Start with the clients your application already uses
AI Logger currently supports direct OpenAI and Anthropic client integrations for custom-built applications and simple orchestration. Calls must pass through the wrapped client to be captured. Frameworks that create and manage their own internal clients, including LangChain, require a separate integration.
const client = aiLogger.autoLog(openai);Frequently asked questions
Does AI Logger stop hallucinations?▾▴
No. AI Logger records captured inferences so a team can reconstruct and verify what happened. Accuracy testing, guardrails and human review remain separate controls.
Does AI Logger explain why a model produced an answer?▾▴
No. It records the input, output and related metadata. That evidence can support an investigation, but it is not a faithful explanation of hidden model reasoning.
What does independently verifiable mean?▾▴
AI Logger hashes the captured record and anchors proof through Integritas on the Minima blockchain. A verifier can compare the later record with that proof. If the content has changed, the result will not match.
Does plaintext leave my application?▾▴
No. Input and output are hashed and encrypted inside the application before transmission. The backend stores hashes and ciphertext.
Which providers are supported?▾▴
The current automatic logging integration supports direct OpenAI and Anthropic clients. Custom-built agents and simple orchestration can use those wrapped clients.
Does it work with LangChain?▾▴
Frameworks that create their own internal model clients require a separate integration. Contact us to discuss your architecture.
What happens if a call bypasses the wrapped client?▾▴
That call is not captured. Coverage should be tested as part of deployment and documented in the audit trail.
Is AI Logger an observability platform?▾▴
It is a focused evidence layer. It can complement observability, governance, SIEM and provider dashboards rather than replace them.
Does AI Logger make us compliant?▾▴
No single SDK can do that. AI Logger can support traceability, record integrity and evidence requirements while your legal, risk and governance teams determine which obligations apply.
Why use blockchain?▾▴
The blockchain stores proof rather than prompts. It provides an independent, timestamped reference that does not depend on the application database remaining unchanged.
Your AI will get something wrong. Keep the receipts.
Instrument one supported system and generate your first verifiable report.