Skip to main content
Ancha tests AI agents against stateful replicas of the tools they use. Each replica answers like the real API, starts with fictional company data and changes as your agent acts. The agent reads and writes the replica instead of the real service. You give the agent a task and choose how many attempts to run. Every attempt starts from a fresh copy of the same data. Checks decide whether each attempt passed, and ancha explain shows what the agent did when one fails.

How it works

  1. Choose a world: the tools and the starter data the agent works with. The starter data is a fictional company, Acme, and its customers, such as Ridgeway Robotics.
  2. Write the task, for example “answer the newest question in #support”.
  3. Run the test. Ancha starts your agent once per attempt and puts tool URLs and fake credentials in its environment variables.
  4. Read the verdict. Checks compare the final tool state and the agent’s API calls with what you expected. ancha explain shows expected versus actual and the calls behind each failure.

Tools

Ancha replicates 38 tools: Slack, Discord, Twilio, Gmail, Google Drive, Google Calendar, Microsoft Word, Notion, Airtable, Dropbox, Resend, GitHub, Datadog, Sentry, PagerDuty, Better Stack, Linear, Jira, Asana, Okta, Amazon S3, Clerk, HubSpot, Salesforce, Attio, Intercom, Zendesk, Gong, Stripe, PayPal, Shopify, Lob, Google Analytics, Google Ads, LinkedIn Ads, ChatGPT Ads, Open-Meteo and Kalshi. Each replica implements a documented subset of the real API. See Tools for what each one covers.

Two ways to run

The CLI needs no account. Signing in at app.ancha.io adds a hosted workspace with a browser console.

Start here

Quickstart

Install the CLI, run an agent, break it and read why it failed. About five minutes.

For coding agents

The commands, JSON output and exit codes a coding agent needs, plus a prompt to paste.

Concepts

Worlds, tests, runs, attempts and checks.

CLI reference

Every ancha command and flag in version 0.1.4.

What to expect

  • Replicas implement a documented subset of each API. A call outside that subset returns the tool’s own error shape, and ancha run lists it as a coverage gap.
  • Your agent must read tool URLs and credentials from the environment variables Ancha sets. Ancha cannot redirect an agent that hardcodes production URLs.
  • Starter data is fictional. Reporting data in the ads and analytics tools is historical and does not grow when your agent changes a budget.