Skip to content
IrogentIrogent

Agent finance, made readable

Explore agent identities, supported assets, credit positions and payment records on Robinhood Chain.

Explore AgentsHow It Works

What Irogent reads

ERC-8004 identities · USDG settlement · Priors credit · x402 payments

Public contracts and feeds, read directly. Not partnerships.

How it works

Four records.
One readable profile.

Irogent starts at an agent’s ERC-8004 identity and follows it into the records that describe its finances. Every figure keeps the source and the block it was read at.
One identity

  1. 01

    Identity

    Who the agent is

    The ERC-8004 registry: who owns the identity, which wallet it declares, and what its own registration file claims.

  2. 02

    Assets

    What it owns

    ETH and USDG read on-chain. Other ERC-20 tokens listed by the indexer, then re-read on-chain.

  3. 03

    Credit

    What it owes

    Priors credit lines: principal outstanding, open loans, due dates and the repayment record.

  4. 04

    Payments

    What it settled

    x402 settlements reported by the facilitator, checked against USDG transfer receipts.

01 · Identity

One identity.
A financial record.

On Robinhood Chain an agent’s identity is an ERC-8004 token: an NFT in the identity registry, named by three parts, the chain, the registry and the agent id. Irogent starts there and follows the identity to the wallet, credit and settlement records that belong to it.

The addresses around an identity are not equal. The owner holds the NFT. The declared agent wallet is set in the registry with that wallet’s own signature. Anything named only in the agent’s registration file is a claim the agent made about itself.

Identity key

eip155:4663Chain0x8004A169FB4a3325136EB29fA0ceB6D2e539a432Identity registry462Agent id

A bare agent id is not unique: the chain and the registry are part of the name. Agent 462 in the verified identity registry is used as the example throughout these pages.

  • Identity owner

    ownerOf(agentId) · holds the NFT

    Controls the identity. One owner can hold many identities and unrelated funds.

    Verified on-chain

  • Declared agent wallet

    setAgentWallet · signed by that wallet

    The address the identity names for its payments, proven by the wallet’s own signature in the registry.

    Verified on-chain

  • Metadata claims

    registration file · written by the agent

    Addresses and services the agent describes itself with. Shown, never used for figures.

    Unverified claim

Attribution

  1. 1Figures belong to the declared agent wallet when one is set.
  2. 2Without one, they belong to the identity owner, and are labelled as the owner’s.
  3. 3Every profile states which address it read, and why.

02 · The record

Owns. Owes. Has done.

Three questions every agent profile answers from the chain. Each panel says where its figures come from, and what it cannot see.

Holdings

Owns

What the attributed address holds now, read at a pinned block.

ETH
Read on-chain
USDG
Read on-chain, verified contract
Other ERC-20s
Blockscout list, re-read on-chain
No price available
Quantity shown, no value

A balance that could not be read is Unknown, never zero.

Liabilities

Owes

What the identity owes on its Priors credit line, read from the pool at a stated block.

Credit line
Priors pool v2 and lens
Principal outstanding
Open loans on the line
Due dates
Per open loan
Repayment record
Indexed loan events

“No credit line found” appears only after a successful read. A failed read is Unknown.

Activity

Has done

What the identity and its wallet have done on-chain, newest first.

Identity
Registration, wallet changes
Credit
Borrowed, repaid, defaulted
Settlements
x402 via the facilitator
Transfers
USDG in and out

Every row links to its transaction on the explorer.

03 · Payments

Follow the flow.

An x402 payment leaves evidence in two places: the HTTP exchange that asked for it, and the transaction that settled it. Irogent keeps them apart and says which one a figure rests on.

Off-chain · request context

Seen by the client and the server only.

  1. 01

    Request

    An agent calls a paid HTTP endpoint.

    GET /resource

  2. 02

    402 challenge

    The server answers Payment Required, naming the price, the asset and the recipient.

    HTTP 402

  3. 03

    Signed payment header

    The agent retries with a payment header carrying a USDG authorization it signed (EIP-3009).

    authorization + signature

On-chain · proof

Anyone can check it in the transaction receipt.

  1. 04

    Settlement

    The facilitator submits the authorization to USDG in a transaction of its own.

    transferWithAuthorization

  2. 05

    Receipt

    The receipt holds the proof: payer, recipient and amount in the logs.

    AuthorizationUsed · Transfer

Request context is shown only when a provider publishes it. The Priors facilitator’s settlement feed does not, so Irogent leaves it out rather than reconstructing it.

Three categories, kept apart.

01On-chain transfer

Confirmed USDG transfer

Evidence
A Transfer log from the verified USDG contract, in a mined transaction.
Does not prove
Why the money moved. A USDG transfer is not automatically an x402 payment.
02Provider-reported

Provider-reported x402 settlement

Evidence
A row in the Priors facilitator’s public settlement feed: payer, recipient, amount and transaction hash.
Does not prove
That the transaction matches the report, until its receipt has been checked.
03Confirmed on-chain

On-chain-confirmed x402 settlement

Evidence
The reported transaction’s receipt matches payer, recipient and amount, with AuthorizationUsed beside the Transfer.
Does not prove
That the paid request was fulfilled. Settlement is not delivery.

A USDG transfer is not automatically an x402 payment.

Settlement does not prove the request was fulfilled.

04 · Live preview

The record, as the app reads it.

Not a mock-up. This panel is rendered from Irogent’s read API on this deployment, with the same components the app uses. When a source is down or still indexing, it says so.
IrogentIrogentLive records
Robinhood Chain · 4663

Chain head

Integrations

Full status

Newest x402 settlements

Directory · newest identities

Open the directory

Live records from Irogent’s read APIStatus read —Settlements read —Directory read —

05 · Developer access

Read the same records over HTTP.

Everything the app shows comes from a public, read-only JSON API. No key is needed. Every answer arrives in one envelope, so the sources, the read-at block, the coverage and any warnings travel with the data.

Envelope fields

  • data
  • sources
  • updatedAt
  • indexedThroughBlock
  • coverage
  • warnings
  • pagination
Read the API reference

  • GET/api/agents

    Indexed directory of ERC-8004 identities

  • GET/api/agents/{chainId}/{registry}/{agentId}

    Identity, roles and attribution/credit/activity/payments

  • GET/api/address/{address}

    Wallet profile and the identities it holds/assets/transfers

  • GET/api/payments

    x402 settlements with on-chain status

  • GET/api/search?q=

    Address, agent id, transaction or name

  • GET/api/status

    Chain head, indexer and integrations

Token · $IROGENT

One contract, not yet deployed.

$IROGENT will live on Robinhood Chain (chain id 4663). The contract address will be published on this page and in the footer first. Until then there is no $IROGENT contract, nothing to buy, and anything claiming to be it is not ours.

Contract address

CA · Soonnot deployed yet

Ticker
$IROGENT
Chain
Robinhood Chain · 4663
Standard
ERC-20
Status
Soon
Token page

What will be published

  • The verified contract address, with its Sourcify record and explorer link.
  • Name, symbol, decimals and total supply, read on-chain at a stated block.
  • Supply and distribution details, together with the contract and not before.

No contract yet

There is no $IROGENT contract, presale or sale today. A contract address you see elsewhere is not ours until it appears on this page.

Identity, assets, credit and payments, read from ERC-8004, USDG and x402 records, with sources on every figure.

Start with one agent

Inspect an agent’s financial footprint.

Look up an agent by name, id or wallet. Every profile states its sources, the address it read and the block each figure comes from.

Explore Agents