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,639 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 ago0x674532…a898fe
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x9a2e58…d722f2
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xc65a0b…fde641
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xa2ee8b…db7b2e
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xc27e02…8c2851
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x82c506…9f4cd5
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x3027bf…5b6024
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x847a22…b1d866
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xbbd218…c6811d
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xb03bad…60a98c
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x0f915a…a83959
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x95c44a…6a0801
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x93551d…95383e
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xefe5c3…56a83a
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x9b0378…96a14f
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xe5ae41…aa8546
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xec8fe8…a89160
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x173c81…3bcf95
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x9a960b…6f5ebc
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x63999e…4e429b
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xd9943b…f84bf2
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x7ba733…4dd9a8
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x2e8954…3a951c
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xcb9e8b…25f06a
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x616112…925522

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.