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.43M Roundhouse has indexed across 1,401,575 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%daydreams352d ago0x08ed21…7d29d9
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams352d ago0xa9f110…d57298
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams352d ago0x5ef505…4abe2a
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams352d ago0x464293…35694a
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams353d ago0x05a15e…a82300
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams353d ago0x800495…49721b
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams353d ago0xf15759…9fbdc4
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams353d ago0x962fb4…fea88c
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams353d ago0xdcdfee…bb9dfe
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams354d ago0x5c4ce3…4b2434
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams354d ago0x02a35d…304ed1
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams354d ago0x5f9008…647664
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams355d ago0xbb457b…d3954b
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams355d ago0xee5bf9…39453a
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams355d ago0xfd1ead…1ba786
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams355d ago0x4a0b05…fed3f9
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams356d ago0xdf86a0…8a50d8
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams356d ago0xd0e40c…3689f0
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams356d ago0xc74df0…680083
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams356d ago0xbd6796…32e347
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams356d ago0x4d81c0…b1f9e3
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams357d ago0xee2ad6…8b121b
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams357d ago0x9b8c13…1b722e
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams358d ago0xf79d1b…6a4f85
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams358d ago0x5bdc20…4b9929

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.