AgentReport

0xa167…dd10

0xa1674b4cf4f215ae0ed9eaabe09c13dfd1c3dd10Explorer
Paid out
$8.62
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
370
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $8.62 of the $3064.22M Roundhouse has indexed across 1,399,799 wallets — less than 0.0001% of it.

Whole-history totals from the index rollup, which can be up to 30 minutes behind.

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

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

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

  • 0xef43…6c7f · last paid 109d ago
    $8.61
    370 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
0xef43…6c7f$8.61$0.00370109d 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 370 observed settlements.

Organic volume $8.62 of $8.62 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x16430f…9d98c8
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xa45ca5…a4d337
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xbd4162…5b1068
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x0e8684…45ec8a
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xf4cc9a…a4734f
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x4369f7…f6bdc4
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x8cdada…191cac
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xb8c7fb…548be8
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x560108…c315b8
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x646776…1e2313
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xb7e8be…f2330c
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x737df0…bb1f3c
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x9066ed…16b9b0
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xd89470…19b6a4
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x33d297…023d3d
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x74f448…7e9be9
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x88ecaf…d16bf0
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xd1e513…7f8c18
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x6df622…a6546a
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xc380c1…238c03
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x3b14d6…6c934b
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x39305d…ed5708
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xcf5867…c7da88
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x54d598…8a0127
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x6d1768…b9af6a

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

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

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: 0xa167…dd10

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