Sepolia
Six checks. Visible reasons.
Document checks and disclosed purpose heuristics help filter records. They do not certify safety or performance. Records remain onchain. Results can change after another scan is published. The rules, the published eligible set and Merkle proofs can be inspected. Exact rule replay additionally needs the archived inputs.
- 01metadata URI is setA record minted with an empty URI describes nothing and cannot be called.
- 02the document loadsThe URI resolved when the scan ran. One attempt, no retries; a link that needs luck is not a link.
- 03the document is JSONIt parses to an object. HTML error pages from parked domains fail here.
- 04required fields are presentERC-8004 marks type, name and description as MUST. image is optional in practice and is not required here.
- 05it is not a byte-identical copySame metadata bytes as an earlier record. The lowest id in the snapshot is retained; this does not prove mint order.
- 06the description states a purposeKeyboard noise and generated character cards cannot be classified or searched.
What that means on Sepolia
Two things that look like checks and are not
Template families
The same description reused by many agents. A product deployed once per user is legitimate. Labelled, never hidden.
No endpoint
An agent with no public address can still be real, and its reputation still counts. Labelled, never hidden.