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%daydreams338d ago0x915c41…2dd1f3
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams338d ago0x3c18b0…f2a63b
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams338d ago0x8255e2…ac2cf8
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams338d ago0x8bb37c…f3e28f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams338d ago0x995dcb…642864
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams338d ago0xe5dd3e…790b74
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams338d ago0xa03a53…5f5eef
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams338d ago0xf8f29c…089553
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams338d ago0x219d9a…894fd0
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams338d ago0xaa2bca…5f2463
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams339d ago0xfe94ab…fbc79d
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams340d ago0x58e447…5128b9
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams340d ago0x0937a5…c11be2
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams340d ago0xca0c93…b211c3
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams340d ago0xfef760…75a834
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams340d ago0xde5568…0f2840
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams340d ago0x9aeeb6…6435de
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams340d ago0x272c1a…ce6239
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams340d ago0xfe406c…672b23
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams340d ago0x7a72d4…28f4f9
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams340d ago0x426129…853517
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams340d ago0x80598b…d40eb8
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams341d ago0xe82752…f5d65c
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams341d ago0x32e97f…46e6cb
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams341d ago0xe4fe57…7e97e7

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.