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%daydreams348d ago0x4f9624…35214c
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams348d ago0x8d8741…da31ae
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams348d ago0x9085de…a38862
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams348d ago0x472361…dd0e26
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams349d ago0xae88ec…7ceaf8
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams349d ago0x9b2c32…d4c690
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams349d ago0x2101a1…f9802b
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams349d ago0x30335e…b91563
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams350d ago0x91b40b…e0d347
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams350d ago0x1e4e81…5edecf
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams350d ago0x6148c3…d8af2b
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams350d ago0x342eaf…2a98e5
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams351d ago0x6323d8…5a1ae6
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams351d ago0x2a5c07…992280
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams351d ago0xcf58ae…88bfaa
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams351d ago0x298c9b…8d5fd8
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams351d ago0x6711d7…c45698
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams351d ago0xf3350a…672a4e
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams351d ago0xdeaa8a…4fee33
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams352d ago0xc17316…c9dfd8
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams352d ago0xa9cd11…abcd69
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams352d ago0xd3b78c…bfa42b
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams352d ago0xe4ee26…fc63aa
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams352d ago0xfd131a…7d51fb
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams352d ago0x3d1e5a…d23ac4

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.