An ERC-8257 entry commits a hash of the tool's manifest on-chain. That commitment is only worth something if somebody actually re-fetches the manifest and re-computes the hash — otherwise the registry is a list of promises. This page runs that check on every entry, including entries that have nothing to do with scry, and reports what it finds either way.
The registry contract is OpenSea's reference deployment (—), the same CREATE2 address on Ethereum, Base and RH-Chain. scry does not run its own — a second registry would fragment the standard. Verification is a fact about bytes, never a score: a meter reading cannot put a tool on this page, move it, or take it off.
| tool | creator | manifest | access | check |
|---|---|---|---|---|
| reading the registry from RH-Chain… | ||||
Anyone may register. There is no gate, no application, and nothing to buy — the registry is permissionless and so is this reading of it.
/.well-known/ai-tool/<slug>.json.keccak256(RFC-8785-JCS(manifest)).registerTool(uri, hash, address(0)) on
the registry — one transaction on RH-Chain.scry holds no key and cannot register on your behalf. The full recipe, with scry's own manifests and their exact hashes, is at /api/opensea; the machine-readable form of this page is /api/tools. New to the chain? /api/rh has the add-chain params.