AEVS icon

AEVS

AEVS is a developer tool for recording and verifying AI agent tool calls with signed, tamper-evident receipts. It helps developers inspect what an agent actually executed through an API or explorer instead of relying on model text alone.

AEVS

What AEVS is

AEVS, the Agent Execution Verification System, is a developer tool for recording and verifying what an AI agent actually did during tool use. The homepage positions it as a way to verify actions rather than relying on model-generated text or chat history.

The product wraps agent tool calls in signed, tamper-evident receipts. Each receipt can include the tool name, inputs, output, timing, errors, and chain metadata, and it can be checked later through an API or a web explorer using a reference ID. The site also shows a Python quickstart and examples for LangChain, with support noted for MCP as well.

AEVS gives teams control over how much information is exposed from each receipt. Public receipts show full payloads, private receipts hide payloads from the public while preserving them for the account, and proof-only receipts keep only hashes and metadata so sensitive inputs and outputs are not stored.

Core capabilities

Capture every tool call

AEVS sits between an agent and its tools so each invocation is captured as it happens, including tool name, inputs, outputs, timing, and errors.

Sign and chain receipts

Receipts are ECDSA-signed with P-256 and linked into a hash chain so changes, omissions, or reordering are easier to detect.

Verify independently

A reference ID can be verified through the public API or the explorer without rerunning the agent, which makes validation separate from execution.

Work with supported frameworks

The SDK can auto-detect LangChain and MCP, and the homepage also shows a LangChain-specific setup example.

Control receipt visibility

Receipts can be configured as public, private, or proof-only, letting teams choose how much payload data is stored or exposed.

Inspect receipts in the explorer

The explorer lets users search by receipt or reference ID and review verification status, chain data, and tool details.

Common use cases

  • Audit agent actions

    Use AEVS when you need evidence of what an agent actually executed, including the tool used, inputs sent, and output returned.

  • Verify actions independently

    Use the verify API or explorer to confirm a receipt from a reference ID in CI, review workflows, or auditor-facing checks without re-running the agent.

  • Control what reviewers can see

    Use the visibility settings to share full payloads for demonstrations or collaborative reviews, while keeping production receipts private or proof-only.

  • Add verification to an agent app

    Use the Python SDK and LangChain example to add signed receipts to an existing agent app without changing the underlying tools.

Pros and Cons

Pros

  • Records tool calls as signed receipts instead of relying on model text alone.
  • Supports independent verification through an API or explorer using a reference ID.
  • Shows configurable receipt visibility for public, private, and proof-only use cases.
  • Provides a clear Python quickstart and LangChain example.
  • Supports tamper-evident chaining with ECDSA P-256 signatures and hash links.

Cons

  • The source does not document pricing or packaging.
  • The available pages provide only a limited view of supported integrations and operational limits.
  • The public material shown here does not include setup prerequisites, security certifications, or deployment details.

FAQ

How do you set up AEVS?

AEVS is configured in code with an API key and agent ID. The homepage shows a Python quickstart using `aevs.configure(...)` and `aevs.enable()` for auto-detection, plus an example for LangChain.

Which frameworks does AEVS support?

The homepage shows support for LangChain and MCP, with a quickstart example for LangChain and a note that `aevs.enable()` auto-detects `langchain` and `mcp`.

What does AEVS capture for each agent action?

AEVS records one receipt per tool call, including the tool name, inputs, output, timing, errors, signature, and hash-chain data. Receipts can be viewed through the API or the explorer.

How do you verify a receipt?

The verify API can confirm a receipt by `reference_id` without needing to rerun the agent, and the explorer lets you search by `reference_id` or `receipt_id`.

What does AEVS cost?

The source does not show pricing, and the pricing URL returns a 404. The homepage and public docs shown here do not describe a pricing model.

Quick Facts

Category
Developer Tool
Product type
Agent execution verification system
Primary users
Developers building AI agents
Frameworks shown
LangChain, MCP
SDK language shown
Python
Source domain
aevs.fetch.ai