AgentReport

0x47be…0b80

0x47bef573b4457b1411468eeb52c7126029dd0b80Explorer
Paid out
$0.52
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
515
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.52 of the $3187.31M Roundhouse has indexed across 1,434,866 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (515)

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%$0.525152

$0.52 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.

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.

  • 0xfe80…47ee · last paid 40d ago
    $0.35
    349 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9c95…e299 · last paid 84d ago
    $0.17
    166 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

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

Funds flow over time

Activity

MayJunJulAugSepOctNov
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xfe80…47ee$0.35$0.0034940d agoGraph
0x9c95…e299$0.17$0.0016684d agoGraph

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

Data quality

68% of observed volume is with a single counterparty, in all 515 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0xe39d31…f7bbb3
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x7cafa2…764256
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x1c1d62…bbc552
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x3627bc…39c254
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0xbafe76…7acd25
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x1b8d8b…786c87
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x10a34b…7cec83
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0xeaf9b0…4fb63b
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0xcdd798…300fca
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0xc40835…b03409
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x1f2225…a616a9
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x141011…6beb35
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa64d ago0x28ead4…ec58af
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0xb0d576…a087d4
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0x9ad68e…caa2f3
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0x7f1580…dda3ff
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0xb913ec…c41476
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0xfbba8b…f56f29
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0x12fbd4…aa2750
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0x8057ff…ed8f40
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0x1ab5f3…c483e8
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0xc85f61…9bd903
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0x789547…319ba0
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0x1d5dfa…91a5a0
0x47be…0b800xfe80…47eeBaseBase$0.001100%fluxa65d ago0xd98e4b…2b17a5

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

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

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: 0x47be…0b80

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