Skip to main content

Continuous evals for agents

Turn your workflows into challenges.

Then test every agent change against them before it ships.

Versalist Challenges page showing workspace navigation and challenge cards.

Works with your stack

Bring your own agent.

Versalist runs any agent harness that starts from a shell. No SDK, no framework adapter: your harness reads the challenge files and writes its output.

Connect your harness

Setup guides for

Models from OpenAI, Anthropic and Google.

The problem

A better average can still ship a worse agent.

An overall score can rise while individual cases get worse. A release review shows both versions case by case, so you see the drop before your users do.

Without Versalist

  • Spot checks on a handful of examples
  • One average score that hides what got worse
  • Release calls made in chat, with nothing on record

With Versalist

  • Both versions run on the same test cases
  • A lower dimension score is flagged as a regression
  • Ship, Hold or Needs work, recorded with the review

How it works

From change to decision in three steps.

  1. Define the test

    Turn a real workflow into fixed test cases and a scoring rubric your team agrees on.

  2. Compare versions

    Run both versions on the same cases and model. Read the scores case by case and dimension by dimension.

  3. Decide and ship

    The review owner records Ship, Hold or Needs work, and can export the review.

See a sample comparison

Features

What a release review puts in front of you.

Scores for both versions, the regressions between them, and every decision made on the review.

  • Side-by-side scores

    Scores for both versions, per case and per rubric dimension. A review holds up to 500 case rows and 100 dimensions per run.

  • Regression flags

    A comparable dimension score that drops is marked as a regression.

  • Like-for-like comparisons

    Both runs must share the challenge, skill, rubric and case identifiers. A missing model identifier does not prove the models match.

  • Decisions on record

    Ship, Hold or Needs work, saved with the evidence and the full decision history.

  • Print and export

    Print a review or export it to Markdown for your release notes and sign-off.

  • Shared with your organization

    Share a review with your organization, or create a public link for eligible reviews.

The platform

Where a release review gets its inputs.

Use Continuous Evals on its own, or with the rest of Versalist. Challenges fix the cases. Skills hold the revisions. Continuous Evals compare them.

Versalist Skills

A private registry for your team's agent skills. Publish a version once and everyone pulls the same one. Roles and review policy decide who can publish, and every rollback is recorded with a reason.

revision · file digests · rollback reason

Versalist Challenges

Challenge programs on your team's real workflows. Each challenge fixes the task, the cases, the rubric and the execution policy, which is what lets two runs be compared.

cases · rubric · execution policy

Versalist Tools

A free directory of tool contracts. See what a tool can do and what access it needs before your agent calls it, and verify contract exports in your browser.

Browse Tools

Security

Review access and data handling

Reviews start private. Owners control how they are shared.

  • Private by default

    Reviews start private. Owners can share with an organization or create a public link for eligible reviews.

  • Secure credential storage

    Model-provider keys are stored per user in Google Secret Manager.

  • Scoped, revocable API keys

    Give each integration only the access it needs, and revoke it at any time.

  • No prompt text in traces

    Trace capture stores prompts as hashes, never as text, and never records model reasoning.

  • Locked evidence

    The evidence behind a review can’t be edited, and decisions are added, never overwritten.

  • Your production runtime

    Versalist never operates your production agent.

Get started

Start with one workflow.

We scope one workflow with you, set up the cases and review the first comparison together.

  1. Scope

    Pick the workflow and agree on what good looks like.

  2. Set up

    Prepare your agent’s skill and model, and turn real cases into a test suite.

  3. Compare

    Score every candidate version against the one you run today.

  4. Decide

    Make the release call and share the results with leadership.

What you’ll need

  • A pilot owner, about an hour a week
  • One engineer for setup, one to two days
  • One security review session

Need to make the case internally? Build your business case

Frequently asked questions

Can’t find what you’re looking for? Talk to our team.

Request a demo
A release review for AI agents. Before a change ships, your team sees the version you run today and the new one side by side, case by case, and records Ship, Hold or Needs work with the evidence.