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 $3069.68M Roundhouse has indexed across 1,403,034 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%daydreams348d ago0x9872b0…7231eb
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams349d ago0x27fd40…c6d654
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams349d ago0x84ee74…c747c5
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams349d ago0x336e65…955231
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams349d ago0x3df39f…16d885
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams349d ago0x8fafc3…891e3f
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams349d ago0xd2a7c7…8d6f6f
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams349d ago0x37403f…b5a9ea
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams349d ago0xaf6df7…540eca
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams349d ago0x63de52…45894d
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams349d ago0x6efbbc…36718c
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams350d ago0x2deebc…9709b0
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams350d ago0xf239cf…2bd822
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams350d ago0x2f2eb9…939877
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams351d ago0x204e53…f67ac3
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams351d ago0x7beb9c…9abdc9
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams351d ago0x25be74…dc6f01
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams351d ago0xc532fb…31854e
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams351d ago0x94d0f7…ba1366
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams351d ago0xffb1dc…db36f0
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams351d ago0x49a9f3…578d16
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams352d ago0xb0c5f3…b3808d
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams352d ago0x1aa684…4dfb6f
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams352d ago0x3f5a5d…733b21
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams352d ago0x3890e7…91a2bb

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.