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%daydreams337d ago0xb4c191…e78818
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams337d ago0x46efa0…2b3207
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams337d ago0x8d42f7…2c500f
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams337d ago0x8573fa…cfe0f4
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams338d ago0x548441…d27f9b
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams338d ago0x62db36…04f05a
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams338d ago0x55cf3b…4f39f0
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams338d ago0x98bb6d…692e9c
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams338d ago0x875f70…88d814
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams339d ago0xf450d5…60db03
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams339d ago0x0e9e1e…e659ca
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams339d ago0xf8a1b0…2aaf3f
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams339d ago0x47cb6c…649f41
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams339d ago0x87aff9…ab86c6
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams340d ago0xffb6db…92b011
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams340d ago0xb1ab28…7ae948
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams340d ago0x0bf241…ae82c0
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams340d ago0x673e55…f848ff
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams340d ago0xa5196a…dd027e
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams340d ago0xc37252…6f2e54
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams340d ago0x85f306…c1d0c9
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams340d ago0x68fc1f…4c6208
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams340d ago0x946558…bcd5cc
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams340d ago0x52f6c5…79b4e7
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams341d ago0xd1530e…e31101

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.