Post-market AI surveillance · Clinical vendor platform
Prove what your AI actually did.Down to a single inference.
Veritrace sits beside a vendor inference stack and captures what production actually did. After a model or prompt change, a reviewer can pin the questions that matter, replay every recorded answer, and see whether the sources moved or the model did. The signed record is what you show when a health system, a regulator, or your own board asks about a specific case.
SHA-256 + Ed25519
Every entry hash-chained to the one before it and signed, with an endpoint that verifies the chain independently.
Release-pinned
Baselines locked to a prompt version, so traffic from the release you are testing cannot quietly become the new normal.
Async by default
Capture runs outside the clinical request path. If ingest fails, your product does not.
Product targets, not measured results or SLAs: drift detection inside 48 hours, 95%+ coverage of production inferences, under 10% false-positive rate on flagged deviations.
One-command setup
Run the wizard in your repo
Answer a few prompts, sign in in the browser, and we create your deployment and ingestion key. The SDK installs automatically and you get a starter file ready to wire into your inference handler.
- No manual copy/paste of API keys in the default flow
- Auto-detects Python, Node, Go, or Java
- Summary checklist shows exactly what was created
Platform
Capture. Analyze. Attest.
Three capabilities that turn post-market surveillance from a manual scramble into continuous, defensible evidence.
Capture
An SDK decorator or a signed API call, running outside your clinical request path. Single inferences or full agent traces, each carrying its release and prompt version.
Hover to explore
Analyze
Deterministic rules catch structural drift: length, citations, required elements, repetition, and source recency. Independent judges score a rubric; grounding checks the cited passage. On a pair, attribution says whether sources moved or the model did.
Hover to explore
Attest
Hash-chained, signed records with a verification endpoint and exportable audit packages. Evidence a reviewer can check independently, not a log they have to trust.
Hover to explore
Release maintenance
Did the evidence change, or did the model?
Creation is the easy part. After a model bump, a reviewer needs to know whether the output moved because the sources moved. Pin the question, replay it, and separate those two things.
Pin the questions that matter
A monitored question set is the contract for a release. After a model or prompt change, you replay the same questions instead of sampling new chat.
Replay every recorded answer
Oldest to newest, with the prompt version, model version, and cited sources on each run. No live re-generation required.
See what actually moved
On a flagged pair, Veritrace attributes the drift: sources changed, the model or prompt changed, both, or neither.
Replay · warfarin + sertraline
Three recorded answers. What moved is labeled on each step.
- Jun 20263.1.0Monograph 2026-03Baseline
- Jul 20263.1.0Monograph 2026-06Sources
- Aug 20263.2.0Monograph 2026-06Model
Dashboard
Built for a vendor product team
After a model bump, a production reviewer confirms or dismisses what drifted. This is not a personal chatbot and not an EHR install.
Flagged Output
Triage by severity, assign a reviewer, and see what moved: sources, the model or prompt, both, or neither.
- Cardiology · length spikeHigh
- Oncology · citation dropMed
- Pediatrics · pattern missLow
Surveillance Config
Clinical and editorial templates. Absolute bounds, required citations, source recency, judge rubrics, and grounding — no engineering ticket.
- Cardiology baselineActive
- Anticoagulant classActive
- Emergency triageDraft
Release Comparison
Pair the same question across any two releases. Unpaired questions stay unpaired instead of being forced into a version story.
- Paired on query_id124
- Sources changed18
- Model or prompt only7
Pinned questions
The monitored set you replay after every release. Oldest answer to newest, with prompt, model, and cited sources on each run.
- Warfarin + SSRI bleeding risk13 runs
- Apixaban renal dosing8 runs
- Lactation counseling4 runs
Provenance
Look up one inference and walk the signed chain: capture, classification, detection, and review. Recent flagged rows are a starting point.
- inference.capturedValid
- deviation.detectedValid
- deviation.reviewedValid
Agent monitoring
You cannot govern what you cannot reconstruct
When a multi-step agent produces a bad answer, the failure is rarely in the final message. It is in the retrieval, the tool call, or the reasoning three steps earlier. Logging the response captures the answer and loses the path that produced it.
Health AI governance frameworks have started asking vendors to log tool access, memory, and actions for agentic systems. Veritrace captures the whole trace as it runs, so that question has an answer months later — not just a summary of what the agent said.
- Every step, in order
- Each step is linked to its parent and stamped with an ordered index, so the path can be replayed exactly as it ran.
- Tool calls, not just messages
- Retrieval, lookups, and external calls are captured as first-class steps with their name and payload.
- Surveillance that follows the trace
- A step inherits the surveillance profiles matched by its root, so a rule written once applies down the whole tree.
- Chained to the audit record
- Root and steps are written in one transaction, with audit entries appended in the same order they executed.
- 0rootAnticoagulant interaction check
- 1retrievaldrug_monograph.search
- 2tool callinteraction_check(warfarin, …)
- 3reasoningRank by severity, filter by renal fn
- 4synthesisCitation not present in source
One flagged step, four steps of context, and an audit entry for each one — reconstructable long after the conversation is over.
Integrations
Live traffic today. History tomorrow.
Instrument production inference with the SDK or Direct API. Backfill archived logs without re-running models. Same audit chain, same surveillance profiles — whether the traffic arrived a minute ago or came out of an archive.
Python SDK
Decorator-based capture with auto-hashing, citation features, and buffered ingest — the fastest path for new services. Repo install today; PyPI pending.
Learn moreDirect HMAC API
Signed POST /v1/inferences for certified JVM cores, batch replay scripts, and languages without a generated client.
Learn moreHistorical import
Upload JSONL or CSV from the dashboard — or drive /v1/import/jobs programmatically. Archived rows keep their original timestamps, accepted up to ten years back.
Learn moreConnectors
Catalog for Postgres, warehouses, and object storage. Export to JSONL today; direct wiring when your stack needs it.
Learn moreGlobal coverage
Surveillance that scales with every deployment
Monitor inference streams across specialties and release trains from a single pane of glass. Veritrace is built to map production activity across markets and model variants so drift does not hide in a single segment.
- Historical backfill from JSONL, CSV, or the import job API
- Continuous capture across vendor inference pipelines
- Same question replayed across releases, with source-vs-model attribution
- Tamper-evident provenance for a single inference, on demand
Region analytics on the roadmap. Globe is illustrative.
Loading globe…