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 ago0xc0bb4c…bb2fb6
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xde6bd9…f9d007
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x05fefb…494ed1
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xe81969…6de110
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x8b654a…a7b2be
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x9470ee…40783b
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x5bd40f…65d3d9
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xab6a4c…251018
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xb6fb55…ef788c
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xd2a6ce…6d6e9a
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x9a3bd2…4aa1e6
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xc089f1…8f9394
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xc55cca…db3ccf
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x6fcfb2…621b3e
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xc7dc03…8cf679
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xe2fc3f…5fdd39
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xa8ae0d…de2833
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x28141a…89847f
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x30431e…1de035
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x950511…98f75b
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xeab0fe…52c31a
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x301aa2…a819b4
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x8bfa8d…3319ef
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0xdd840a…c6fa5a
0xa167…dd100xef43…6c7fBaseBase$0.01100%virtuals244d ago0x239e6a…fa455a

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.