Check the agent before you hand it work
Identity, data sources and profile changes of AI agents on Robinhood Chain, read from public data, kept as separate facts.
Intora reads public Robinhood Chain data and the agent's linked metadata. It does not run agents, hold funds or issue credit, and it guarantees nothing. No token is needed to use it.
Scroll to begin
01 / 04
Enter the identity
An ERC-8004 agent id, the address an agent pays from, or the link to its metadata file. One box takes all three.
What a check reads
Identity registry
001
Reads
- ownerOf
- tokenURI
- getAgentWallet
- Registered events
- Transfer events
- balanceOf owner
What Intora does
Run a checkCheck workspace
Enter an agent id, address or metadata link. Sixteen checks come back as separate facts, each with its source and what it cannot tell you.
Change watch
Keep agents on a local list. Each visit compares the owner, wallet, metadata hash, code and roles with your last look and lists what moved.
Saved reports
Every check can be saved in this browser and downloaded as JSON. The report hash is keccak-256 of its canonical text, so anyone can recompute it.
Check book
An on-chain book for report hashes: a reviewer files and revises, a second wallet marks it reproduced or not, the agent's owner can answer.
Separate facts, a public record
— newest registration: not read yet.
— in the last 50,000 blocks. Anyone can register an id; a count says nothing about quality.
No score. Sixteen checks stay sixteen separate facts. Nothing is weighed, summed or turned into a safe or unsafe label.
Does not run agents, lend or hold funds. Intora only reads. The check book stores hashes and links, never money.
The check book is not deployed yet. Until it is, reports are saved in your browser and as files, and every check still works.
Evidence, then judgement
Where the identity meets the evidence
The decision to give an agent a task or a budget stays yours. Intora puts what the public record shows next to what it cannot show, so that decision starts from facts instead of a profile page.
Who it is for
For the people who hand agents work. Not a verdict on the agent.
Operators
Before an agent gets a task, an API key or a spending allowance: who owns its identity, where it pays from, and what changed lately.
Reviewers
Write down what you checked and when, publish the hash, and let a second wallet mark it reproduced or different.
Developers
Read the same facts from your own code. The report format, the status codes and the contract are open.
Agent owners
See your agent the way others will. If a report about it is filed in the book, answer it from the owner wallet.
The sources we read
Public data, with its limits
Everything a check shows comes from a public source you can open yourself. Each line names it, and every fact says where its reach ends.
Robinhood Chain
Contract reads, code, storage slots and logs through the chain's RPC, relayed by this site. Log history is read in windows the node accepts; any block range it refuses is named.
ERC-8004 registries
The identity registry at 0x8004A169… holds agent ids, owners, wallets and metadata links. Registering is open to anyone.
Sourcify and Blockscout
Whether source code is published for the bytecode, the contract name and its creation record. Blockscout is read only when the site has a key.
Metadata hosts
The agent's registration file, fetched once over https or an ipfs gateway, hashed, and read as data. Nothing in it is followed or run.
Run a check
Start with one identity
Paste an agent id from the ERC-8004 registry, the address an agent pays from, or its metadata link. The check reads public data only.