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 $3069.68M Roundhouse has indexed across 1,403,034 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%daydreams341d ago0xbaf898…aee122
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams341d ago0x711793…21935d
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams341d ago0xcf8be5…e3d3ae
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams341d ago0x2073e2…ef5c86
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams341d ago0xa4ed0c…10df66
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams341d ago0xceaf7c…504a85
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams341d ago0x1b223c…54fce6
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams342d ago0x91e831…6cb22b
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams342d ago0x5a865a…16f88b
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams342d ago0x9cd812…aa6932
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams342d ago0xb6a86d…3ae55f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams342d ago0x8f7840…35f993
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams342d ago0xbbf89a…55338f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams342d ago0x0643e5…b6f38b
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams342d ago0x307eb5…f4b04f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams342d ago0x8fdf23…d65ab5
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams342d ago0x77d223…19998b
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams342d ago0x1b24ea…412fb2
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams343d ago0xe0ae97…2a8245
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams343d ago0x4ad9d7…81d279
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams343d ago0x7ac728…635106
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams343d ago0x29f40f…399c30
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams343d ago0xee4381…c0a987
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams343d ago0x031b4a…41bd6f
0x6138…8bbe0x6482…b779BaseBase$0.0001100%daydreams343d ago0x2864fd…14184d

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.