Skip to content

BY CLEARPATH

Know what your AI agents did—and what happened next.

Use the self-service API to follow connected workflows, identify missing outcomes, and review a clear record of actions, retries, and supporting evidence.
Illustrative workflowExample data, not a live record
  1. Workflow started

    09:00:04

    Initiated by a staff user

    Workflow:
    Running
    Evidence:
    Signed
  2. Step completed

    09:00:31

    Research agent

    Workflow:
    Running
    Evidence:
    Signed
  3. Delivery attempt failed

    09:01:12

    Delivery service · attempt 1

    Workflow:
    Retrying
    Evidence:
    Signed
  4. Retry completed

    09:03:12

    Delivery service · attempt 2

    Workflow:
    Running
    Evidence:
    Signed
  5. Expected outcome overdue

    10:00:00

    Outcome monitor

    Workflow:
    Overdue
    Evidence:
    Pending
  6. Outcome received late

    10:42:18

    Receiving application

    Workflow:
    Completed late
    Evidence:
    Signed

Why Witness

When an automated workflow stalls, retries, or reports success without the expected result, teams need to understand what happened, who or what acted, and what evidence is available.

Witness is for businesses using AI agents, teams building automated workflows, and organizations overseeing connected applications. It monitors the activity your connected workflows report; it does not automatically see every action in every system.

How it works

  1. 01

    Connect a workflow

    Configure reporting from a supported application or your own integration.

  2. 02

    Track activity and outcomes

    Follow steps, attempts, responsible actors, and expected results.

  3. 03

    Review the evidence

    Inspect the timeline and available signed records.

Core capabilities

  • Workflow timelines

    Steps, timestamps, initiating users, performing agents or services, and separate retry attempts.

  • Outcome monitoring

    Expected results, missed deadlines, failures, and late completion.

  • Evidence integrity

    Signed records and verification proofs that help detect changes to recorded evidence.

  • Customer access controls

    Organization-scoped applications, workflows, and evidence.

Powered by Trust Ledger

Witness uses Clearpath’s Trust Ledger to sign recorded evidence.

Cryptographic verification supports the integrity of a recorded report. It does not independently prove that an action occurred or that an AI result is correct.

Integrations

  • CompassIP

    Built and tested

    First workflow integration built and tested; customer activation checks are in progress.

  • CaptureIP

    Planned

    Planned integration.

  • Other applications

    API

    Connect your own instrumented workflow using the Witness API documentation.

Start with the API.

Create an account, get a test API key, and connect your first workflow. Choose paid usage when you’re ready.

Free Testing

Test in the sandbox

Self-service sandbox API access. Evidence is labeled “Sandbox — not cryptographically signed,” with no paid signing calls or customer charges.

Paid Usage

Move to signed evidence

Production API access with real signed evidence powered by Trust Ledger, subject to the selected plan’s limits.

Sandbox history is not automatically converted into paid, signed evidence. Ordinary signup and upgrading do not require a call, sales inquiry, or manual approval.

Questions

What can I monitor?

Activity from workflows that are connected and instrumented to report to Witness: steps, attempts, the users and agents involved, and expected outcomes. Witness does not automatically see actions in systems that are not reporting to it.

How do I connect an application?

Create an account, get a test API key, and connect your first workflow. The API documentation explains how an instrumented application reports activity and outcomes to Witness.

Does Witness prevent an agent from taking an action?

No. Witness records and monitors instrumented activity. Your existing application permission controls remain responsible for blocking actions.

What does a verified record prove?

Verification supports the integrity of a recorded report: it helps show the record has not changed since it was signed. It does not independently prove that an action occurred or that an AI result is correct.

How do free testing and paid usage work?

Free testing provides self-service sandbox API access. Sandbox evidence is labeled “Sandbox — not cryptographically signed” and does not use paid signing calls or create customer charges. Paid usage provides production API access with real signed evidence powered by Trust Ledger, subject to the selected plan’s limits. Sandbox history is not automatically converted into paid, signed evidence.