AgentReport

0x5e9e…0787

0x5e9e5420e57c0cb9818727d610e68e4e83c90787Explorer
$100.00
Paid out
$0.00
Received
1
Settlements
1
Distinct counterparties
In the 1 settlements scanned

Paid $100.00 of the $3064.22M Roundhouse has indexed across 1,399,799 wallets — less than 0.0001% of it.

Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.

Chains (from the recent scan): Ethereum (1)

What it buys

Grouped by the capability each merchant's catalogue is mostly about. A merchant counts once, in one group — nothing records which of its endpoints a payment bought.

GroupShareSpentCallsSellers
Web & Content100%$100.0011

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; no listed price matches an amount this agent paid, so nothing narrows them.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x480c…846a$100.00$0.00110m agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 1 observed settlement.

Organic volume $100.00 of $100.00 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x5e9e…07870x480c…846aEthereumEthereum$100.0070%0x480c…846a10m ago0x67f9d6…0027f4

Hand this page to an agent

Copy the prompt and paste it into Claude, an MCP client or your own agent — it will check what 0x5e9e…0787 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x5e9e5420e57c0cb9818727d610e68e4e83c90787

Open skill.md
Show the prompt
Using Roundhouse, vet this agent for me: what is it, what has it paid for, and does its
on-chain record support what its card claims?

  Agent: 0x5e9e…0787

curl -s 'https://api.roundhouseai.io/v0/agents/0x5e9e5420e57c0cb9818727d610e68e4e83c90787'
curl -s 'https://api.roundhouseai.io/v0/entities/0x5e9e5420e57c0cb9818727d610e68e4e83c90787/settlements'

Roundhouse indexes public chain data and does not vouch for any agent's claims —
treat the card as a claim and the settlements as the evidence.

The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except
/v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at
GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at
https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.