Identities without context
A registration is a token id. Who owns it, which wallet it declares and what its file claims are three different facts.
Financial visibility for autonomous agents
Explore agent identities, inspect their assets, and trace financial activity on Robinhood Chain.
Robinhood Chain · 4663 · mainnet · reading head… · read-only
Section 02: The problem
Identity lives in a registry, balances on-chain, history in an explorer index, settlements in a provider feed and claims in a self-reported file. Reading one without the others misleads.
A registration is a token id. Who owns it, which wallet it declares and what its file claims are three different facts.
A number without its block, its source and its coverage is an impression, not a record.
A USDG transfer is not a payment record until a settlement and its receipt agree.
Section 03: The product
Paste an address or an agent id. Input is validated before any request is made; a wallet is never required.
Registered events of the verified ERC-8004 registry, newest first.
Provider-reported rows from the Priors facilitator, each checked against its receipt.
Section 04: Four financial views
Scroll: the ring opens into the four views, connects them to their evidence, and settles into the explorer itself.
Stage 1
An ERC-8004 identity is an NFT in a registry on Robinhood Chain: an id, an owner, an agent URI and an optionally declared agent wallet. Voogent starts from that record and nothing else.
Read from the verified identity registry at a pinned block.
Stage 2
The same identity opens into four questions: who it is, what its linked wallet holds, what it owes in supported protocols, and what it has paid or been paid with verifiable evidence.
Identity · Assets · Liabilities · Payments
Stage 3
Every figure is tied to where it came from: an on-chain read with its block, an explorer index page, a provider feed row checked against its receipt, or a self-reported file that is labelled as such.
Sources, blocks and retrieval times travel with every panel.
Stage 4
The lines settle into the explorer itself. Paste an address or an agent id and inspect assets, liabilities and activity without connecting a wallet.
Live records from the chain, shown below.
Registry reads: ownerOf, tokenURI, getAgentWallet. The registration file is fetched and marked self-reported.
ETH, USDG and WETH read on-chain at one block; other tokens from the explorer index, re-read on-chain.
Priors CreditPoolV2 and CreditLensV2: outstanding principal, open loans and their fees. No invented formulas.
Facilitator settlements matched to receipts: payer, recipient and amount must agree, in a successful transaction.
Section 05: How it works
Resolve, read, prove. No account, no wallet, no interpretation beyond what the sources can show.
01-resolve
Paste an address or an agent id. The registry answers who owns it and which wallet it declares; the self-reported file is fetched, sanitized and labelled.
Waiting for a live read; nothing here is invented.
02-read
Balances and credit-line state are read on-chain at a pinned block, discovered tokens are re-read, and every figure keeps its source.
Waiting for the chain head.
03-prove
A provider-reported settlement becomes a payment only when its receipt holds the matching transfer in a successful transaction.
Waiting for the facilitator feed.
Section 06: Capabilities
Everything Voogent does is a read with a source. Nothing below is a score, a ranking or a recommendation.
Registry reads by id; identities by address through the explorer NFT index and the Priors check API, each confirmed on-chain.
ETH, USDG and WETH at one pinned block; explorer-discovered tokens re-read on-chain; any ERC-20 inspected method by method.
Priors CreditPoolV2 and CreditLensV2: outstanding principal, open loans with fees and due dates, recent history, published score.
Facilitator settlements reconciled with their receipts; a row is x402 only when payer, recipient and amount agree on-chain.
Explorer history joined with token movements; native transfers, token transfers, contract interactions and creations kept apart; paginated.
Profiles saved in this browser only; CSV and JSON exports of exactly the displayed rows with network, source, time and coverage.
Section 07: Four views
Each view answers one question with its own sources, shows a live record read now, and says what it cannot see.
/01 — Who is this?
ownerOf, tokenURI and getAgentWallet from the verified registry at one block; the registration file fetched through a guarded client and shown as a claim.
Section 08: Sources we read
Every name below is a data source Voogent queries, with its live probe result. None is a partnership, sponsorship or endorsement.
Probing each source…
Section 09: Evidence
A queried zero, a missing record, an unsupported integration, a failed request and a stale value are five different things. Every panel says which one you are looking at.
A value read from a contract or account at a block number you can see: balances, ownership, credit-line state, receipts.
Limits. Current state only. A plain RPC cannot list a wallet’s history or enumerate every token it holds.
On-chain record
JSON-RPC at a stated block
Section 10: Token
$VOOGENT will live on Robinhood Chain (chain id 4663). The contract address is not published yet; when it is, it appears here and on the token page first.
Contract address
CA · Soonnot deployed yet
On-chain facts
Section 11: Questions
What Voogent shows, what it does not, and why.
No. An ERC-8004 registration is an on-chain record that an identity exists and who owns it. Voogent shows the record and its evidence; it publishes no trust score, risk score or safety label.
Because the registry does not link it to an identity in the coverage Voogent can check: the explorer NFT index and the Priors check API, both confirmed on-chain. Absence from a partial index is not proof that no registration exists, and the page says so.
Not by itself. A row is labelled x402 only when the Priors facilitator reports a settlement with that transaction hash and the receipt holds a USDG transfer from the reported payer to the reported recipient for the reported amount in a successful transaction.
No. It means the identity is not enrolled in Priors CreditPoolV2 at the stated block. Priors is the only lending protocol Voogent reads; other protocols and off-chain obligations are out of scope, and a failed read is shown as unknown, never as zero.
Because the price feed (DefiLlama) has no quote for that token. Quantities are still shown from the on-chain read. A market price, when shown, is not a redemption guarantee.
A token is planned on Robinhood Chain; its contract address is not published yet (CA: Soon). When it is, it appears on the token page, in the footer and on the landing page first, after an on-chain read of the contract. Inside Voogent the token grants no access, no data advantage and no score: the explorer and every read stay free and open.
A $VOOGENT token is planned on Robinhood Chain; its contract address is not published yet (CA: Soon). When it is, it appears on the token page, in the footer and on the landing page first, after an on-chain read of the contract. Inside Voogent the token grants no access, no data advantage and no score: the explorer and every read stay free and open.
In this browser’s local storage, on this device only. No account, no wallet, no sync. Clearing site data removes it; exports are available as JSON.
Robinhood Chain JSON-RPC, the verified ERC-8004 registries, the Blockscout explorer API, the Priors pool, lens and facilitator, and DefiLlama. Addresses, verification methods and limits are listed on the methodology page, and live health on status.
Start here
Open the explorer, paste an address or an agent id, and read what the chain and its indexes can prove.
Follow @Voogent on X for coverage updates.