# AIzilla CAGE · Agent Claim Checker - Catch False Test Reports (`kotaro-project/agent-claim-checker`) Actor

Check an AI coding agent's final report against what its tools really returned. Flags 'tests pass' with no passing run, 'fixed' with no fail-then-pass, wrong file counts, 'done' with nothing checked after the last change, and edited tests. English and Japanese. No AI calls.

- **URL**: https://apify.com/kotaro-project/agent-claim-checker.md
- **Developed by:** [KOTARO project](https://apify.com/kotaro-project) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 report checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## ✅ Agent Claim Checker — catch AI agents saying "tests pass" when they don't

AI coding agents finish with confident reports: *"Fixed the bug. All tests pass. 2 files changed."* Sometimes the tests never ran, the last run failed, or the agent edited the tests themselves.

**Agent Claim Checker compares the report with what the tools really returned** and tells you which claims are not backed by evidence.

### What it checks

| Claim in the report | Flagged when |
|---|---|
| "all tests pass" / 「テストはすべて通りました」 | no test run in the log, the last test run failed, or test files were edited in the same session |
| "fixed" / 「修正しました」 | there is no failing test run followed by a passing one |
| "N files changed" | N does not match the files actually edited |
| "done" / 「完了」 | nothing ran successfully after the last change |

Works with pytest, npm/yarn/pnpm test, go test, cargo test, jest, vitest, rspec, phpunit, mvn/gradle test and more.

### Input

```json
{
  "report": "Fixed the login bug. All tests pass. 2 files changed.",
  "evidence": [
    {"tool": "Edit", "path": "src/login.py"},
    {"tool": "Bash", "command": "pytest -q", "exit_code": 1}
  ]
}
```

Or send many reports at once in `checks`.

### Output example

```json
{
  "verdict": "unsupported",
  "claims": ["file_count", "fixed", "tests_pass"],
  "problems": [
    {"claim": "tests_pass", "why": "says tests pass, but the last test run did not succeed (exit code 1)"},
    {"claim": "fixed", "why": "says fixed, but the evidence has no failing test run followed by a passing one"},
    {"claim": "file_count", "why": "says 2 files changed, but the evidence shows 1"}
  ],
  "testRuns": 1,
  "filesChanged": 1
}
```

`supported` → the claims match the log · `unsupported` → ask the agent to prove it · `no_claims` → nothing to check.

### Pricing

Pay per checked report (see the Pricing tab). Apart from Apify's standard start fee there is no per-run charge.

### Notes

- Rule-based and fast: it only knows the claim phrases and test commands listed above, so unusual wording can slip through. It checks consistency with the log you give it; it cannot see work that is not in the log.
- Your text is only read inside your run and not sent anywhere else.

Part of **AIzilla CAGE** — guardrail systems for AI coding agents that run on your own machine: https://aizilla.neuro-hive.jp/en/

Made by **KOTARO Data Works** 🇯🇵

# Actor input Schema

## `report` (type: `string`):

The message your AI agent wrote at the end of its work, for example 'Fixed the bug. All tests pass. 2 files changed.'

## `evidence` (type: `array`):

The tool calls in the order they happened. Each item: {"tool": "Bash" or "Edit"/"Write", "command": "pytest -q", "exit_code": 0, "path": "src/app.py"}. Commands need an exit code; edits need a path.

## `checks` (type: `array`):

Optional: a list of {"id": ..., "report": ..., "evidence": \[...]} to check many reports in one run. Each one is billed as one result.

## Actor input object example

```json
{
  "report": "Fixed the login bug. All tests pass. 2 files changed.",
  "evidence": [
    {
      "tool": "Edit",
      "path": "src/login.py"
    },
    {
      "tool": "Bash",
      "command": "pytest -q",
      "exit_code": 1
    }
  ]
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "report": "Fixed the login bug. All tests pass. 2 files changed.",
    "evidence": [
        {
            "tool": "Edit",
            "path": "src/login.py"
        },
        {
            "tool": "Bash",
            "command": "pytest -q",
            "exit_code": 1
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("kotaro-project/agent-claim-checker").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "report": "Fixed the login bug. All tests pass. 2 files changed.",
    "evidence": [
        {
            "tool": "Edit",
            "path": "src/login.py",
        },
        {
            "tool": "Bash",
            "command": "pytest -q",
            "exit_code": 1,
        },
    ],
}

# Run the Actor and wait for it to finish
run = client.actor("kotaro-project/agent-claim-checker").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "report": "Fixed the login bug. All tests pass. 2 files changed.",
  "evidence": [
    {
      "tool": "Edit",
      "path": "src/login.py"
    },
    {
      "tool": "Bash",
      "command": "pytest -q",
      "exit_code": 1
    }
  ]
}' |
apify call kotaro-project/agent-claim-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,kotaro-project/agent-claim-checker"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/KcVj0S0yYoenhRKEF/builds/JiT5UsEypZZD99XfK/openapi.json