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%daydreams343d ago0x1aae2d…743387
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams343d ago0xc90f48…341003
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams343d ago0xe8a897…bca6b0
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams343d ago0xbea0e2…a36367
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams344d ago0x102c42…2e56dc
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams344d ago0x8f3b09…d4fd31
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams344d ago0x9a5989…c5edcf
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams344d ago0xef1bb2…2d1449
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams344d ago0xd536d0…880df1
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams344d ago0x77d69d…14a6b6
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams344d ago0xfe8b28…a39e3a
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams344d ago0xffb08e…48c5b9
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams344d ago0xe4bed5…b4d46d
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams344d ago0x134900…964515
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams344d ago0x379a48…cb45bd
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams345d ago0x9c3d49…daf486
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams345d ago0x2c919f…fe6318
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams345d ago0xc08e1b…42bd45
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams345d ago0xadf1d7…206150
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams345d ago0x109a3b…bb722c
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams345d ago0xed6dc9…b6c5aa
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams345d ago0x924a8a…2c2ff6
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams345d ago0xef97e1…8d8500
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams345d ago0x3b741e…afd17b
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams345d ago0x1067d2…1f7dcf

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.