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,563 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%daydreams323d ago0xbdef11…5242e0
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams323d ago0xd17480…355657
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams324d ago0xa6c79f…889d1a
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams324d ago0xb79a9c…16175f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams324d ago0x531a9e…cac493
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams324d ago0x306517…18da51
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams324d ago0x75f126…abf3bd
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams324d ago0x338610…d84f15
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams324d ago0x5e91f5…c7328e
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams324d ago0x31911f…58096c
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams324d ago0x9044ab…88cc0c
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams325d ago0xd7a8bc…3f478f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams325d ago0xa9254c…d67fe5
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams325d ago0xe09844…7106dd
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams325d ago0x38460a…41c955
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams325d ago0x76df43…2dc5c5
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams325d ago0x1e8cb4…414d7f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams325d ago0xc2234d…b09c36
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams325d ago0x3513ea…72d283
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams325d ago0xe05019…a2f38b
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams325d ago0xbe6a57…145f3b
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams325d ago0x504b5d…7bd6c7
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams326d ago0xb5ec22…3e3eef
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams326d ago0x598867…c97e88
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams326d ago0x156865…43a15d

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.