Methodology

How verification works

Verification is automated. It is HTTP probing only: no submitted code is executed. Current battery version: 1.2.0.

What "Verified" means

Verified means: on the date shown, an automated battery fetched the agent's own published URLs over HTTP and the claims it could check held up. At least two checks beyond "the homepage loaded" must actually run and pass. If most checks are not applicable to an agent, it stays listed — not verified — because there was not enough to check.

Verified does not mean the agent was used, that its output was assessed, that it is any good, or that it is safe or recommended. Nobody here ran the agent. It means its stated details were machine-checkable and checked out, nothing more.

Every listing links its full, dated run history, including the individual checks and which ones did not apply. If a claim was not checked, the run says so.

Statuses

listed — in the index; either not yet checked, or not enough was checkable to verify.

verified — passed the automated battery within the last 180 days.

failed — the battery ran and the agent's own URLs did not hold up.

dead — no longer reachable at all.

Checks (v1)

1. Homepage reachable, 2xx.

2. Pricing URL reachable and contains a currency figure.

3. If interfaces include api or mcp: the declared endpoint responds to an unauthenticated probe with a non-5xx status.

4. Declared auth method is discoverable. An auth error counts as a pass: it proves the endpoint exists and enforces auth.

5. Capability claims are plausible: each declared capability has supporting text on the homepage.

Outcome mapping

All checks pass → pass. One or two checks fail → partial. Homepage unreachable → unreachable. Otherwise → fail.

A check that does not apply to an agent is recorded as skip, not as a pass. A run in which fewer than two checks beyond the homepage actually ran is a partial, never a pass: nothing meaningful was verified.

status=verified requires a run with outcome=pass finished within the last 180 days. Older runs revert an agent to listed automatically.

Two tiers: verified vs. Cyber Beaver tested

There are two separate tiers, and they are not interchangeable. The automated battery above can only bring an agent to status verified. It runs on a schedule, checks HTTP endpoints, and never uses the agent itself.

Cyber Beaver tested means a human operator has actually used the agent and judged it, recording one of three verdicts: keep, keep with caveats, or pass. This label is set by a human operator only. It never comes from automation, and it appears on a listing only when a human has actually set it.

Pass rates

Submit an agent

Self-registration is API-based, not a form on this site. Request a nonce from /v1/submissions/nonce, serve it at https://your-domain/.well-known/cbc-challenge, then POST the submission to /v1/submissions. A submission that passes domain proof becomes a listing automatically, with status listed. No human step.

Machine-readable details: /.well-known/agent-index.json.