AgentReport

0x6031…c2d1

0x6031551fc1fe26710fe4b20316d5dc91d9d6c2d1Explorer
Paid out
$18.14↓ 40%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
2125↓ 60%
Last 7d vs prior 7d
273
Distinct counterparties
Over the whole indexed history

Paid $18.14 of the $833.92M Roundhouse has indexed across 1,300,305 wallets — less than 0.0001% of it.

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

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 & Content85%$8.107934
AI & Media6%$0.61232
Not in any catalogue4%$0.42243
Location & Weather3%$0.27162
Crypto Markets1%$0.1131

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 12 of 12 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 1,000 most recent settlements of 2,125 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not. One merchant publishes more endpoints than a single catalogue read returns; its list is partial.

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

Funds flow over time

Activity

AprMayJunJulAugSepOct
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x9636…c397$7.75$0.0077512h agoGraph
0x66d7…83bc$0.31$0.0095d agoGraph
0xdadc…b9df$0.30$0.00145d agoGraph
0x2b6d…32c5$0.17$0.00115d agoGraph
0x2ec4…be71$0.17$0.001716h agoGraph
0x2583…967e$0.17$0.0065d agoGraph
0x03d7…584c$0.13$0.0056d agoGraph
0x1b25…964a$0.12$0.0025d agoGraph

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

Data quality

71% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x6031…c2d10x9636…c397Base$0.01100%coinbase12h ago0xed0d6c…55174c
0x6031…c2d10x9636…c397Base$0.01100%coinbase12h ago0x1da2fd…c86d31
0x6031…c2d10x9636…c397Base$0.01100%coinbase12h ago0x0a126f…1a387e
0x6031…c2d10x9636…c397Base$0.01100%coinbase12h ago0xe97bf2…d50c33
0x6031…c2d10x9636…c397Base$0.01100%coinbase12h ago0x87b2c5…8a19b0
0x6031…c2d10x9636…c397Base$0.01100%coinbase12h ago0x265531…dafa31
0x6031…c2d10x2ec4…be71Base$0.01100%coinbase16h ago0x641ee5…0b07d4
0x6031…c2d10xabf4…a9d0Base$0.001100%coinbase18h ago0xe5bb29…8c5a21
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0xa870e5…5d9a04
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0xcb0c10…af4203
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0x2e74d8…d8777a
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0xf2582a…960f59
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0xe263a9…147c43
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0xfc9b22…16f6b5
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0x52c606…bcbfc0
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0xd5b1ad…5b0e9d
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0x389cd2…d96079
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0x25ff44…b41425
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0xdfbbe4…84ce17
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0x78fbd7…e87d0c
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0xff5739…ec638b
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0x1d33f8…b86a47
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0x0efda5…75dff1
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0x97082c…c338e7
0x6031…c2d10x9636…c397Base$0.01100%coinbase18h ago0x971397…e31b24

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

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

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: 0x6031…c2d1

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