AgentReport

0xb7f7…3685

0xb7f70602857f417e165c2c070f2a8ba330e83685Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
260
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,396 wallets — less than 0.0001% of it.

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

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.032601

$0.03 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.

  • 0x6482…b779 · last paid 276d ago
    $0.03
    260 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
0x6482…b779$0.03$0.00260276d 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 260 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams346d ago0xaf36b0…e95490
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams346d ago0x83035c…e7404f
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams347d ago0x441749…b0beeb
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams347d ago0xf1a9d9…4e75c0
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams347d ago0x600a32…f68c75
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams347d ago0x9a07dd…df53aa
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams347d ago0xc95052…19f740
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams347d ago0x897600…0ef997
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams347d ago0x981af1…b1f813
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams347d ago0x373529…2cff62
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams348d ago0xfcb413…41bea5
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams348d ago0xb22dbf…1685fd
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams348d ago0xce59a5…f542aa
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams348d ago0xcf18d1…84a057
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams348d ago0xef509f…f226f1
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams348d ago0xd5368f…59e4fe
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams348d ago0xbf8664…568d3a
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams348d ago0xe96805…badd21
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams348d ago0xf4bdb3…7343e1
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams348d ago0x043d96…2b338f
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams348d ago0xd20870…2c7d4e
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams349d ago0xd4017b…6419c3
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams349d ago0x187d0b…647cee
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams349d ago0x58ec62…f6aa95
0xb7f7…36850x6482…b779BaseBase$0.0001100%daydreams349d ago0x5b1d03…309fd9

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

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

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: 0xb7f7…3685

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