AgentReport

0x8869…2cd3

0x8869ab8e5b6c8ae6a2f6263be717342494572cd3Explorer
Paid out
$1.47
Last 7d vs prior 7d
Received
$1.47
Last 7d vs prior 7d
Settlements
4
Last 7d vs prior 7d
3
Distinct counterparties
Over the whole indexed history

Paid $1.47 of the $3059.84M Roundhouse has indexed across 1,397,384 wallets — less than 0.0001% of it.

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

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

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

  • 0xb7b8…f330 · last paid 128d ago
    $0.98
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0xe650…5ff9 · last paid 60d ago
    $0.49
    1 call

    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
0xc49a…9d2f$0.00$1.47260d agoGraph
0xb7b8…f330$0.98$0.001128d agoGraph
0xe650…5ff9$0.49$0.00160d agoGraph

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

Data quality

50% of observed volume is with a single counterparty, in all 4 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x8869…2cd30xe650…5ff9BaseBase$0.49100%fluxa60d ago0x29e3bd…e08ac8
0xc49a…9d2f0x8869…2cd3BaseBase$0.49100%fluxa60d ago0x668ca8…cdc595
0x8869…2cd30xb7b8…f330BaseBase$0.98100%fluxa128d ago0x9c74b0…99a2d7
0xc49a…9d2f0x8869…2cd3BaseBase$0.98100%fluxa128d ago0xa1bb1f…2cd62a

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

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

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: 0x8869…2cd3

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