AgentReport

0xe29e…4503

0xe29e5b17067b061cc2adfc8a18a02417a8c24503Explorer
Paid out
$67.94
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
181
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $67.94 of the $261.19M Roundhouse has indexed across 717,123 wallets — less than 0.0001% of it.

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

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

$67.94 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 243d ago
    $67.94
    181 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$67.94$0.00181243d 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 181 observed settlements.

Organic volume $67.94 of $67.94 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0xfe6918…d852d0
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x67daef…de9d7a
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x07ff1e…16a307
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0xa26858…012185
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x075b59…bd70de
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0xb44d50…5a271a
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x6f10e2…b5d28e
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x51844a…d0edc7
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x4a279c…a96b74
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x73ff2d…049091
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x3be6b4…8e5b06
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x0f4bac…8ea5e1
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0xfa3a8d…2bfcaa
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0xf0e84c…b5a4b5
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0xb3f4e0…9fc493
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0xeaaa7e…dc12eb
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x2b9dee…b30d36
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x5c2ac6…bb4403
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0xca8b96…8d93e5
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x41580f…c2bd0d
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0xcd8029…e15b62
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0xe581cc…62f73d
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x2e39fe…62919c
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0x49f1f2…7b6b9a
0xe29e…45030xef43…6c7fBase$0.50100%virtuals243d ago0xd7d581…d209f8

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

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

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: 0xe29e…4503

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