AgentReport

0xe13d…f542

0xe13d5f93d2b4231477722d4f75e8729ea51cf542Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
267
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3068.58M Roundhouse has indexed across 1,402,722 wallets — less than 0.0001% of it.

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

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

$0.03 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.

  • 0x6482…b779 · last paid 277d ago
    $0.03
    267 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
0x6482…b779$0.03$0.00267277d 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 267 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams346d ago0x0fbc8f…bf64f7
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams346d ago0x50bbd1…5a69bf
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams346d ago0x7137b7…410991
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams346d ago0xa6afc2…dabb36
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams346d ago0x00a9d5…f8be08
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams346d ago0xaf37bb…227866
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams346d ago0xc7c14d…15ab3c
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams346d ago0x9969cd…4945d1
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams346d ago0x44fff0…ad0d56
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams347d ago0x56517a…bf78f1
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams347d ago0x24a32d…58203d
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams347d ago0x672637…6fa4ae
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams347d ago0xa1785c…9944c7
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams347d ago0x6d7c42…687804
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams347d ago0x380a6f…863c2d
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams347d ago0x78a051…226deb
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams348d ago0x657d8d…9dfb29
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams348d ago0x5b22ac…d0917d
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams348d ago0x82f880…14c805
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams348d ago0xd9e2a3…8d15f6
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams348d ago0x54aa9c…8ac8c8
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams348d ago0x582918…8ec659
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams348d ago0x27236d…7e0944
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams348d ago0x8735d2…1d9acd
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams348d ago0xd96a99…264cc7

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

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

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: 0xe13d…f542

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