日本語
verify/operators
free, read only, no account

You run a server. Being measured costs nothing.

There is no application to review, so there is nobody to persuade and no reason to charge you. Measurement is free and always will be. What you can pay for is being told the moment something changes, and being told exactly what to change when it does.

Measure a server now What the five conditions measure The badge
Three steps

No account, no fee, no waiting list

  1. Put your endpoint in front of the gate

    It reads initialize and tools/list, and it reads your agent card. It calls none of your tools. Ten seconds, nothing installed, nothing signed.

  2. Read the verdict, and the hash under it

    Every verdict carries a record_sha256. Recompute it before you believe us. A verifier you have to trust is not a verifier.

  3. Fix what is not met, and be measured again

    Nothing here is reviewed by a person, so there is no appeal to write. Change the condition and the next sweep says so.

When a condition is not met

What to change, condition by condition

01 · endpoint
The gate could not complete initialize and tools/list from the public internet. Common causes: the server only listens locally, the transport is stdio rather than HTTP, or a proxy in front is rejecting an unauthenticated read.
02 · identity
Serve /.well-known/agent-card.json with at least a name and a description, as JSON, over HTTPS.
03 · disclosure
Declare paid_by, referral_fee and listing_fee on the card. Only silence disqualifies. "referral_fee: none" and "referral_fee: 20 percent" both pass. We are not scoring the answer, only whether it was given.
04 · determinism
Not measured unless you ask for it, because it means executing one of your tools. Ask, and name the tool that is safe to call twice.
05 · recomputable
This one is on us, not on you. If a hash does not recompute, that is our defect.

If you want this walked through against your actual server, that is the paid part: 2.0 hours, itemised, and the conflict of interest named on the page. Before you go there, the three free things on that page solve most rows, and if we think yours is one of them we will say so rather than take the work.

The badge

Drawn when it is asked for, not issued once

There is no procedure for taking a badge away, because there does not need to be one. The image is drawn from the register at request time, so it stops being green the moment your row does.

A saved file is a different thing: it stays green forever. So the saved version carries the date it was measured and the address where the current row lives. A dated snapshot is not a lie. A green rectangle with no date would be.

Badge, live and downloadable Be told when a condition flips
One thing you should know

Anyone can put a server in front of this gate, including one they do not own. That includes yours, and it includes ours. The check is read only and calls no tool, so there is nothing there to abuse. But it does mean the register can contain a row you did not create. If that row is wrong, ask for a re-measurement and both results stay published.