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 ago0x516172…1fafcf
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x6c724b…6144ab
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x30fa95…d9f621
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x32de7f…8aa91f
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x703d12…371186
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x49ba1b…094ed6
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xbd73b2…b7c4ee
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xb8b401…803038
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x018657…28d042
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xf46a57…dd2350
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xf59ca8…0cea80
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x6814a3…85e017
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x4a6241…341399
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x7a4c61…b15e48
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x4703f4…5e5ac5
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x5ae537…1f58af
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xb7eebf…2ba6c7
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x034d2f…4d72c4
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x7cfd0b…f9c85b
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x5cca92…7e6ebb
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x1ac2ec…e874c9
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xd00c76…4ad9c5
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x7f6498…646e4b
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x75ae9c…4d2a30
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x65b881…c7a712

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.