AgentCount

Check a registration file before you mint it

The same checker that judged every agent in the census, run against a document you paste. Nothing is stored and no run is written — this answers a question, it does not add you to anything.

spec 68fc6765761a|checker 0.6.0|1 MUST requirement, conditional

Your document

nothing is stored
Paste the registration file you are about to mint. It is sent to the checker, judged, and discarded — no run is written and nothing is kept.
Intended identity
Intended identityoptional — all three, or rung 5 stays unchecked

What the checker says

awaiting a document

Results appear here. The checker answers rungs 3, 4 and 5 — the three a document can be judged on before it exists on-chain. Rungs 1, 2 and 7 need a minted agent, a published URI and feedback respectively, so a draft leaves them unchecked.

Why this exists

In the reference run, 48 agents belonging to 48 unrelated owners all failed rung 4 identically — one hosting service’s template omitted agentRegistry, and nobody found out until after minting. Separately, 10,101 documents from 6,460 owners share one exact set of missing recommended fields, which reads as a widely-copied template rather than thousands of independent choices.

Passing here is not a guarantee about your agent — it is a statement about your document, at this spec pin, today. What each rung measures →