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%daydreams325d ago0xc9b1f6…a7f490
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams326d ago0x74b013…cb2f5f
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams326d ago0xb25d0d…922376
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams326d ago0x92f743…1e72ca
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams326d ago0x96496a…5931ff
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams326d ago0x21dfe1…213291
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams326d ago0x2d33df…681a11
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams326d ago0xd97ee2…2c907d
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams326d ago0x15a6ed…0af794
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams326d ago0x4b3107…aecf50
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams326d ago0xefc615…b048ed
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams326d ago0x79dbc6…a439e9
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams327d ago0xdbe5af…749393
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams327d ago0x968b1a…12a808
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams327d ago0x567840…1719ca
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams327d ago0x1c96da…eff94b
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams327d ago0xfc7615…b98c70
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams327d ago0x69059e…7cb050
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams327d ago0xf58b83…cc55fb
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams327d ago0x59d70c…5309ea
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams327d ago0x8e0374…4d346e
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams328d ago0xd36c52…af054e
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams328d ago0xb4f6ac…2b54fa
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams335d ago0x0f9e40…7ae5c5
0x105d…0d890x6482…b779BaseBase$0.0001100%daydreams337d ago0x48d7ea…082349

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.