AgentReport

0x4041…0270

0x4041e588ddaaaed83b2c8f1467a39e01e10f0270Explorer
Paid out
$160.34
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
587
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $160.34 of the $260.63M Roundhouse has indexed across 716,280 wallets — less than 0.0001% of it.

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

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

$160.34 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 279d ago
    $160.34
    587 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

MarAprMayJunJulAugSep
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xef43…6c7f$160.34$0.00587279d 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 587 observed settlements.

Organic volume $160.34 of $160.34 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0xbf0f5c…63bd22
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0xc5ba14…b345a5
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0x3003bd…c93562
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0x8baf2b…480f1f
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0x7b2149…e49ad4
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0x9082c2…a5d21c
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0x75bf15…a6f752
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0xe09194…b01d8b
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0x26a888…b34df6
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0x24e5cd…197630
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0xed5928…4e87f2
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0x09c894…efee9f
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0xc55e28…aa1a23
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0xadb5ef…5a845c
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0x7ad241…3b58f5
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0xc63db3…e124d9
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0x0b8731…4b8dd6
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0x56ca98…8320ff
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0xda2742…288289
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0x7524f6…b30c08
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0xe29f48…320ab5
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0xb8efe4…b58ff9
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0xd4881e…21e7be
0x4041…02700xef43…6c7fBase$0.05100%virtuals279d ago0x74a5df…9d3567
0x4041…02700xef43…6c7fBase$0.50100%virtuals279d ago0xa46028…dfa9dd

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

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

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: 0x4041…0270

curl -s 'https://api.roundhouseai.io/v0/agents/0x4041e588ddaaaed83b2c8f1467a39e01e10f0270'
curl -s 'https://api.roundhouseai.io/v0/entities/0x4041e588ddaaaed83b2c8f1467a39e01e10f0270/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.