Keep your agents on rails.

Amiril learns what each of your AI agents normally does, flags the runs that don't fit, and explains what went wrong. Where a rule would have prevented it, Amiril drafts one. Your agents check it before every tool call, in microseconds, and it deploys within seconds with no changes to your agents.

Watching refunds-agent, 1284 runs today

22.1Unusual runForgot to check identity before an account changeAccount agent

Your logs say success.

When an agent gets something wrong, it rarely crashes. It refunds the wrong order or skips an identity check, then reports the run as done.

What your logs see

Your logs show thousands of completed runs. The wrong refund is somewhere in there.

What Amiril sees

The three runs least like their agent's usual behaviour, most unusual first.

  • 23.4Refunded the same order twiceRefunds agent20s ago
  • 24.8Processed the wrong refundRefunds agent1m ago
  • 22.1Forgot to check identity before an account changeAccount agent1m ago

Scored by statistics, not by another model.

Amiril learns how each agent usually behaves from its own past runs and scores every new run by how different it is. No AI model decides which runs are unusual.

Same run, same score

A higher score means the run is rarer for this agent. Connect your traces and scoring starts, with no thresholds to tune.

This run23.4Usual range for refunds-agent

No AI grading AI

You can see why every run got its score.

  • The same run gets the same score, every time.
  • Every score shows the usual range it was compared with.
  • Each agent is compared only with its own past runs, the way security teams spot an unusual login.

Read a summary, not a trace

Statistics pick out the few runs worth a look. An agent then explains what happened in each one, so the expensive part only runs where it matters.

From unusual run to draft rule in one click

An agent drafts the rule from the unusual run using our statistical models and evidence, in plain text you can read.

24.8Processed the wrong refundRefunds agent · 2 minutes agoRule drafted
Suggested ruleDraft
refund-needs-identity
when calls "issue_refund"
unless exists "verify_identity"[status ok]
5This would have blocked 5 similar calls in your past runs.

Change how your agents behave without a release.

Rules are settings, not code. Running agents pick them up within seconds, the way they pick up feature flags.

  1. 1Draft

    An agent drafts the rule from the unusual run.

  2. 2Test

    See which of your past runs it would have blocked.

  3. 3Trial

    It checks live runs and records what it would block, but blocks nothing.

  4. 4Turn on

    Your running agents follow it within seconds, with no release.

refunds-agentrun 8f2c41
✻
ThinkingThe customer wants a refund for order #4821. I'll issue it now.

Rules are checked inside your agent.

Each tool call is checked in your agent's own process, so there is no proxy and no network call. The same rule works on any cloud and every framework Amiril supports.

  • Google ADK
  • LangGraph
  • Python and TypeScript
0.1 msmedian time per check in our benchmark
  • AWS, GCP and Azure
  • Your own servers
  • A laptop

Your agents can change real data in production. Watch them as closely as anyone else with that access.

Every check is logged

Amiril logs every tool call it checks, whether it was allowed, flagged or blocked, and the rule that decided it.

Rules you can read

Each rule is plain text, so anyone can see exactly what it allows and blocks.

Approval for risky tool calls

Coming soon. Pause a tool call until a person approves it.

See your agents' dirty work today.

Upload the traces you already have and Amiril shows you every unusual run in them, as far back as your history goes.