AgentReport

0x1309…04b0

0x130959631ec3346c78af495e7ba98abc86d504b0Explorer
Paid out
$0.02
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
246
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.02 of the $3068.58M Roundhouse has indexed across 1,402,396 wallets — less than 0.0001% of it.

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

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

$0.02 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 276d ago
    $0.02
    246 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.02$0.00246276d 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 246 observed settlements.

Organic volume $0.02 of $0.02 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams355d ago0x397036…310a05
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams355d ago0x1ae8c9…7dae72
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams355d ago0x24cfe4…9a5855
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams355d ago0xbff24d…4704b3
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams355d ago0x813219…8690d6
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams356d ago0x63ecb6…9c72b0
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams356d ago0x455d51…4c8a67
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams356d ago0x365b14…e4c9d6
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams356d ago0x40833a…4af823
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams357d ago0x7f569e…acbcd7
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams357d ago0x55d738…22f0e5
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams357d ago0x3ae343…c547db
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams357d ago0x6994a5…dfb913
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams358d ago0x1b027d…cde727
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams358d ago0xb5f68c…095992
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams358d ago0x8dc6d1…48f381
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams358d ago0x90e849…6bd450
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams359d ago0x5b9439…292dd2
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams359d ago0x3df7f3…97ac9e
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams359d ago0xf1cf6a…a6f421
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams359d ago0x35b4eb…350e56
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams360d ago0x56ee7f…e72dbc
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams361d ago0xcbd0a0…d89ae8
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams361d ago0x26ad17…a194bc
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams361d ago0xf63c33…a50a3f

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

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

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: 0x1309…04b0

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