AgentReport

0x72fa…b80b

0x72fa15b139b41acc1cb72f4b9701e8c678bcb80bExplorer
$0.04
Paid out
$0.00
Received
3
Settlements
2
Distinct counterparties
Over the whole indexed history

Paid $0.04 of the $3063.55M Roundhouse has indexed across 1,399,142 wallets — less than 0.0001% of it.

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

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
Reference Data50%$0.0221
Not in any catalogue50%$0.0211

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

  • 0x2932…4f60defi.hugen.tokyoDomain and DNS lookupEndpoint up
    0x2932…4f60 · last paid 138d ago
    $0.02
    2 calls
    ▸56 of 83 catalogued endpoints list a price this agent paid

    75 further catalogued endpoints not listed.

  • 0xdb5a…0671 · last paid 138d ago
    $0.02
    1 call

    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…

Activity

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xdb5a…0671$0.02$0.001138d agoGraph
0x2932…4f60$0.02$0.002138d agoGraph

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

Data quality

50% of observed volume is with a single counterparty, in all 3 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x72fa…b80b0xdb5a…0671BaseBase$0.02100%coinbase138d ago0xccae3e…3a64df
0x72fa…b80b0x2932…4f60BaseBase$0.01100%coinbase138d ago0x8dc041…6236dc
0x72fa…b80b0x2932…4f60BaseBase$0.01100%coinbase138d ago0x532681…4e0242

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

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

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: 0x72fa…b80b

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