AgentReport

0x105d…0d89

0x105db17484ca914f29c550e8baa04ad910c30d89Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
261
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.00M Roundhouse has indexed across 1,401,091 wallets — less than 0.0001% of it.

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

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

$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 276d ago
    $0.03
    261 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.00261276d 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 261 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams341d ago0x6aa4ab…db0221
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams341d ago0x2d748d…962292
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams341d ago0xacddee…4d376a
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams341d ago0x775c3b…13da28
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams341d ago0x2c38f7…af3cf9
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams341d ago0x4259bf…191a02
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams341d ago0xded365…d7ddf8
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams341d ago0x3f5380…c5472f
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams341d ago0x440412…ac24e7
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams342d ago0xc79690…a4be1d
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams342d ago0x83e68b…cfbe56
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams342d ago0xaf4bc6…d88d37
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams342d ago0x0db55c…83a879
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams342d ago0x3a7621…d5fe1a
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams342d ago0x9a1e04…3c5987
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams342d ago0x14f2a1…b620a9
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams342d ago0xb5e0e7…66de04
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams342d ago0x16f5ee…ef74a3
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams342d ago0xc194ee…3a43cb
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams343d ago0x534b4d…502579
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams343d ago0xbfcd5f…9ffa1f
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams343d ago0x966412…c568b8
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams343d ago0x73a18d…a6a654
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams343d ago0x7a92cb…c34226
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams343d ago0xe4d612…a85c6c

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

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

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: 0x105d…0d89

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