# Intora Intel

> Identity, data sources and profile changes of AI agents on Robinhood Chain, read from public data, kept as separate facts. No score, no guarantee; it does not run agents, hold funds or issue credit. $INTORA is not needed.

Check workspace: https://intoraintel.xyz/check?q=<ERC-8004 agent id | 0x address | https/ipfs/data metadata link>
JSON (read-only, rate limited): https://intoraintel.xyz/api/check?q=<same>
Identity registry read: 0x8004A169FB4a3325136EB29fA0ceB6D2e539a432 on Robinhood Chain (4663)
Method and limits: https://intoraintel.xyz/method

## Checks (slot: name, reads)
- 0: Identity registered, Registered event and ownerOf in the ERC-8004 identity registry. Limit: Registration is open to anyone. It proves an id exists, not who runs the agent or what it does.
- 1: Current owner, ownerOf(agentId) at the latest block. Limit: An owner is a wallet. Whether a person, a team or another program holds its key is not visible on chain.
- 2: Owner changes, Transfer events of this agent id after registration. Limit: Counts transfers inside the registry only. A sold or shared private key changes nothing on chain.
- 3: Agent wallet, getAgentWallet(agentId). Limit: The wallet the owner declared for payments. Funds can still move through other wallets.
- 4: Metadata link, tokenURI(agentId), the agent's registration file link. Limit: The link is whatever the owner set. Its host can change the file without any chain event.
- 5: Metadata file and hash, One fetch of the link (https, ipfs through a public gateway, or data:), keccak-256 of the bytes. Limit: The hash is of what this fetch received at this time. Another fetch may get different bytes.
- 6: File names this identity, The registrations list inside the file, compared with this agent id and registry. Limit: The file is written by the owner. Matching ids show consistency, not truth of the description, services or skills.
- 7: Profile changes on chain, URIUpdated and MetadataSet events of this agent id. Limit: Only changes made through the registry are on chain. Edits to the hosted file itself are not.
- 8: Code at the address, eth_getCode: size and keccak-256 of the runtime bytecode. Limit: No code means a key-held account (or a contract not deployed yet). Code says nothing about intent.
- 9: Source published, Sourcify (no key) and Blockscout (when the site has a key). Limit: Published source matches the bytecode. It is not a review of what the code does.
- 10: Deployer and age, Creation transaction from Sourcify or Blockscout; registration block for an agent id. Limit: Known only when a source service recorded the creation. Otherwise shown as not available.
- 11: Upgradeable proxy, EIP-1967 implementation, admin and beacon slots; EIP-1167 minimal proxy pattern. Limit: Other proxy designs exist. A plain contract can also hand control to another contract in its own way.
- 12: Implementation changes, Upgraded and BeaconUpgraded events at the address. Limit: Reads standard events only. A proxy that does not emit them can change silently.
- 13: Owner or admin role, owner() and the EIP-1967 admin slot. Limit: Other role systems are common. Absence of owner() does not mean nobody controls the contract.
- 14: Control changes, OwnershipTransferred, RoleGranted, RoleRevoked and AdminChanged events. Limit: Standard events only. Custom role systems may log differently or not at all.
- 15: Account activity, Transaction count (nonce) and native balance at the latest block. Limit: A count, not a history. Activity says nothing about whether past actions were good.