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 $3068.58M Roundhouse has indexed across 1,402,722 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%daydreams326d ago0x303a0d…7b4a43
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams326d ago0x8baf30…98c4f0
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams326d ago0x160f8e…cc6220
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams326d ago0x0e91bc…00c12f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams326d ago0x64a8a5…2d078a
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams326d ago0xd8cd9a…ac9739
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams326d ago0x458160…20eb79
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams327d ago0xf79878…90ee30
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams327d ago0x27bd8f…77db18
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams327d ago0xba1061…2bdd03
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams327d ago0xf6274b…49f6f6
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams327d ago0x6415df…eceb0b
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams327d ago0xbde6df…7eacc8
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams327d ago0x2cae56…391012
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams327d ago0xa398cc…88c9ba
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams327d ago0xb15827…6e1e47
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams328d ago0x7b38b1…64119d
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams328d ago0xafa49a…129259
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams328d ago0x3444b7…0c675f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams328d ago0xce9291…fba06e
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams328d ago0x4d2fd4…858ed8
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams336d ago0x0e5b63…2152f5
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams337d ago0xbd15b9…747265
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams337d ago0x736167…3c0a24
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams337d ago0x1fb675…eb4abb

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.