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.

Continuous capture
SDK decorator or signed Direct API. Single inferences or full agent traces, including tool calls.
Structural detection
Deterministic rules on length, citation counts, required elements, repetition, and how old the newest cited source is.
Semantic detection
Independent judges against a rubric, grounding against the cited source, and editorial profiles for draft quality.
Tamper-evident audit
A record a reviewer can verify rather than one they have to trust.

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
Integration setup guide
clinical-api - bash

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.

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

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.
POST /v1/inferences/agent_trace
  • 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.

Global 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…