AgentReport

0x2158…724e

0x2158f7b6dead1c1118a832ffe752b86f92fe724eExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
263
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,563 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (263)

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.032631

$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 277d ago
    $0.03
    263 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.00263277d 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 263 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x13a823…dc9151
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x12a702…e381d5
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x8c45ae…c739ca
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x522600…4ecc6a
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x7bde83…f3af61
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x5d74f5…1ad90b
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x08b7f9…346acd
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x48f452…45f47d
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams346d ago0xb0cc7c…cb0c61
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams346d ago0x61f7c3…5f2028
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams347d ago0xa061a3…a62c6a
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams347d ago0x85eeb4…b3279c
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams347d ago0xe0c2f1…fe04d6
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams347d ago0x7a2a32…86ad1b
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams347d ago0x4f18fc…7c2384
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams347d ago0x593d2f…4402fb
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams347d ago0xd70702…eab5fe
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x547b47…410534
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x4f2209…171483
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams348d ago0xb49274…79e2f9
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x7d973b…e02b49
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x9f0468…671cc3
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x5c0f3d…a0dfc6
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams348d ago0x8fcb16…d21e01
0x2158…724e0x6482…b779BaseBase$0.0001100%daydreams348d ago0xa62a92…0c6b31

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 0x2158…724e has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x2158f7b6dead1c1118a832ffe752b86f92fe724e

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: 0x2158…724e

curl -s 'https://api.roundhouseai.io/v0/agents/0x2158f7b6dead1c1118a832ffe752b86f92fe724e'
curl -s 'https://api.roundhouseai.io/v0/entities/0x2158f7b6dead1c1118a832ffe752b86f92fe724e/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.