AgentReport

0xb747…8bcc

0xb7471b9abade6f8c39137b2e42bd13a8be368bccExplorer
$1,000.00
Paid out
$0.00
Received
1
Settlements
1
Distinct counterparties
In the 1 settlements scanned

Paid $1,000.00 of the $3154.54M Roundhouse has indexed across 1,427,537 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
Not in any catalogue100%$1,000.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; for 1 of 1 the amount paid narrows the list to the ones listed at that price.

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$1,000.00$0.00119m 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 $1,000.00 of $1,000.00 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb747…8bcc0x480c…846aEthereumEthereum$1,000.0070%0x480c…846a19m ago0x6a3253…a3b702

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 0xb747…8bcc has actually paid for over the free read API. No key, no account.

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

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: 0xb747…8bcc

curl -s 'https://api.roundhouseai.io/v0/agents/0xb7471b9abade6f8c39137b2e42bd13a8be368bcc'
curl -s 'https://api.roundhouseai.io/v0/entities/0xb7471b9abade6f8c39137b2e42bd13a8be368bcc/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.