AgentReport

0xec35…8289

0xec358ce3e3d6918aa0d5979560e6ea744eaa8289Explorer
Paid out
$2.23
Last 7d vs prior 7d
Received
$1.11
Last 7d vs prior 7d
Settlements
25
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $2.23 of the $846.56M Roundhouse has indexed across 1,329,848 wallets — less than 0.0001% of it.

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

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%$2.2051

$2.20 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.

  • 0xbb1d…64e4 · last paid 441d ago
    $2.20
    5 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

MayJunJulAugSepOct
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xbb1d…64e4$2.20$1.0823427d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

1 self-dealing settlement (payer = payee) observed; 99% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 24 observed settlements.

Organic volume $3.29 of $3.31 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xbb1d…64e40xec35…8289Base$0.0170%0xe890…f632427d ago0x528b4c…78c145
0xec35…82890xec35…8289Base$0.0270%0xe890…f632434d ago0xc43f31…fa9dc9
0xbb1d…64e40xec35…8289Base$0.0170%0xe890…f632434d ago0x782ac6…2082f0
0xec35…82890xbb1d…64e4Base$0.0170%0xe890…f632441d ago0x0e9a04…091993
0xbb1d…64e40xec35…8289Base$0.0170%0xe890…f632448d ago0x219e81…127e40
0xec35…82890xbb1d…64e4Base$1.0370%0xe890…f632455d ago0x240d32…944386
0xbb1d…64e40xec35…8289Base$0.00231170%0xe890…f632455d ago0x4f3c76…ac47c6
0xbb1d…64e40xec35…8289Base$0.1470%0xe890…f632462d ago0x709638…d14a76
0xbb1d…64e40xec35…8289Base$0.0270%0xe890…f632462d ago0xcbc778…bb072e
0xbb1d…64e40xec35…8289Base$0.2970%0xe890…f632469d ago0xba34ed…82146d
0xbb1d…64e40xec35…8289Base$0.0170%0xe890…f632469d ago0x574941…7613d9
0xec35…82890xbb1d…64e4Base$0.1470%0xe890…f632469d ago0x768809…e033f2
0xbb1d…64e40xec35…8289Base$0.0370%0xe890…f632483d ago0x60ec0f…bea267
0xbb1d…64e40xec35…8289Base$0.0970%0xe890…f632483d ago0x2314af…a5338a
0xbb1d…64e40xec35…8289Base$0.0270%0xe890…f632490d ago0xecb1ac…e66311
0xbb1d…64e40xec35…8289Base$0.0670%0xe890…f632490d ago0x0752b8…d397e8
0xbb1d…64e40xec35…8289Base$0.1670%0xe890…f632504d ago0x658098…533932
0xbb1d…64e40xec35…8289Base$0.1570%0xe890…f632504d ago0xdacc53…a148bb
0xbb1d…64e40xec35…8289Base$0.0270%0xe890…f632510d ago0x7bac3a…dbb9b6
0xec35…82890xbb1d…64e4Base$0.0270%0xe890…f632510d ago0x4034af…a7a573
0xbb1d…64e40xec35…8289Base$0.0170%0xe890…f632525d ago0xd6ad2b…3d6107
0xbb1d…64e40xec35…8289Base$0.0170%0xe890…f632525d ago0x542f74…cc9990
0xec35…82890xbb1d…64e4Base$1.0070%0xe890…f632530d ago0x034a5f…e3a8e4
0xbb1d…64e40xec35…8289Base$0.0170%0xe890…f632532d ago0x2c3cde…dab2aa

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

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

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: 0xec35…8289

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