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.25M Roundhouse has indexed across 1,401,192 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%daydreams345d ago0x406c93…031687
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams346d ago0x9dfadd…3f4847
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams346d ago0x4213de…cb4583
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams346d ago0xb5bd92…4656e7
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams346d ago0xdd5949…6b4e54
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams346d ago0xd073de…4da22a
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams346d ago0x00a6f3…b4eae7
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams346d ago0x69ef1a…c48ece
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams346d ago0x85bdcf…b158f9
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams346d ago0xdadd98…4e3d5d
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams346d ago0x800058…034130
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams347d ago0x4f1440…1f786a
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams347d ago0x60e9ce…74042e
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams347d ago0x6b73e5…372a52
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams347d ago0x5ef418…1a31df
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams347d ago0x5ece18…92c438
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams347d ago0x028cb8…6ba066
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams347d ago0x74f498…f939a4
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams348d ago0xa31dca…8dda48
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams348d ago0x935272…3fd986
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams348d ago0xa0a1bc…bb9277
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams348d ago0x86e115…d3b801
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams348d ago0x4b4cb8…d74d1d
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams348d ago0xa1d99f…549011
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams348d ago0x7ac5a5…de4516

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.