AgentReport

0x6138…8bbe

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

Paid $0.03 of the $3070.29M Roundhouse has indexed across 1,403,290 wallets — less than 0.0001% of it.

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

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

$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 277d ago
    $0.03
    270 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.00270277d 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 270 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams352d ago0x4d92de…8cf4fc
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams352d ago0xc9a89e…552718
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams353d ago0xe80dab…5fdbd4
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams353d ago0x30e330…6010a5
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams353d ago0x2d925f…20085f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams353d ago0x97524b…530296
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams353d ago0x4517e6…972235
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams353d ago0x796039…ee1cf8
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams353d ago0x5e900f…a3fc37
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams353d ago0x5dfc02…a03baa
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams354d ago0xceee2d…7635fd
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams355d ago0x5932a4…278a90
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams355d ago0xbda34b…201811
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams355d ago0x1e470d…b66ea1
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams355d ago0x9c387e…38a62a
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams355d ago0x27ed49…3f19e5
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams355d ago0xdc834c…54f54d
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams355d ago0x54fb47…17b666
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams356d ago0x72da4b…d1dc37
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams356d ago0x9b4675…bd8da9
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams356d ago0xb27047…e8e33f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams356d ago0xb72b80…80b0a9
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams357d ago0xa8eee9…b83c4b
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams357d ago0x656163…a4a0b3
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams357d ago0x9b7314…5f1b54

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

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

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: 0x6138…8bbe

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