AgentReport

0x52af…b768

0x52af3e6d13f7c13ec887a2e69058a1432aa5b768Explorer
Paid out
$275.01↓ 55%
Last 7d vs prior 7d
Received
$47.94
Last 7d vs prior 7d
Settlements
24903↓ 55%
Last 7d vs prior 7d
8
Distinct counterparties
Over the whole indexed history

Paid $275.01 of the $832.32M Roundhouse has indexed across 1,296,850 wallets — less than 0.0001% of it.

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

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 catalogue92%$9.209201
Crypto Markets8%$0.80801

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

Folded from this wallet's 1,006 most recent settlements of 24,903 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.

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
0x44ad…4700$9.20$0.0092039m agoGraph
0xdb3f…feb1$0.00$7.99114d agoGraph
0x8f73…68e4$0.00$7.99114d agoGraph
0x94ce…0e9a$0.00$7.99114d agoGraph
0xcb03…3283$0.00$7.99114d agoGraph
0x6a87…6797$0.00$7.99114d agoGraph
0xe5b8…c474$0.00$7.99114d agoGraph
0x8aab…ce15$0.80$0.008042m agoGraph

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

Data quality

Not enough of this address's history was examined to assess it: self_dealing and counterparty_concentration and single_counterparty were computed over the 1006 most recent settlements scanned (its history is longer than the 2000-row scan cap), so nothing found there rules anything out. This is an incomplete check, not a clean record.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x52af…b7680x44ad…4700Base$0.01100%coinbase39m ago0xfe590f…5caf0e
0x52af…b7680x44ad…4700Base$0.01100%coinbase40m ago0x42796b…dbcd5f
0x52af…b7680x44ad…4700Base$0.01100%coinbase41m ago0xb14ee7…609cef
0x52af…b7680x44ad…4700Base$0.01100%coinbase42m ago0xb82e02…e8e258
0x52af…b7680x8aab…ce15Base$0.01100%coinbase42m ago0x3efa5d…b954ed
0x52af…b7680x44ad…4700Base$0.01100%coinbase43m ago0xedfde1…aa8e98
0x52af…b7680x44ad…4700Base$0.01100%coinbase44m ago0x5f1cf7…3eb769
0x52af…b7680x44ad…4700Base$0.01100%coinbase44m ago0x79ce3c…821982
0x52af…b7680x44ad…4700Base$0.01100%coinbase45m ago0x8f6b0c…47aff4
0x52af…b7680x44ad…4700Base$0.01100%coinbase45m ago0xca9879…697dab
0x52af…b7680x44ad…4700Base$0.01100%coinbase46m ago0x9cd8c5…465138
0x52af…b7680x44ad…4700Base$0.01100%coinbase46m ago0xe624cf…48e0b4
0x52af…b7680x44ad…4700Base$0.01100%coinbase47m ago0x45fb41…2a5d5b
0x52af…b7680x44ad…4700Base$0.01100%coinbase47m ago0xa681a7…a3778d
0x52af…b7680x44ad…4700Base$0.01100%coinbase48m ago0x764db1…56d1d6
0x52af…b7680x44ad…4700Base$0.01100%coinbase48m ago0x3e8a1e…af61e8
0x52af…b7680x44ad…4700Base$0.01100%coinbase49m ago0xfbc21c…8c17b3
0x52af…b7680x44ad…4700Base$0.01100%coinbase49m ago0x4a4a05…520efc
0x52af…b7680x44ad…4700Base$0.01100%coinbase50m ago0x571d6b…ab55e2
0x52af…b7680x44ad…4700Base$0.01100%coinbase50m ago0x2cd899…6dfb0b
0x52af…b7680x44ad…4700Base$0.01100%coinbase51m ago0x817d9c…9bdace
0x52af…b7680x44ad…4700Base$0.01100%coinbase51m ago0xe2a9af…e6d00b
0x52af…b7680x44ad…4700Base$0.01100%coinbase52m ago0xbb7448…0d19ea
0x52af…b7680x8aab…ce15Base$0.01100%coinbase52m ago0xe3827d…47412f
0x52af…b7680x44ad…4700Base$0.01100%coinbase52m ago0xd41c5d…2f2e02

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

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

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: 0x52af…b768

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