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,563 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 276d 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.00267276d 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%daydreams338d ago0xa60e42…606c95
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams338d ago0x0239be…992bd0
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams338d ago0x835a57…e3dcc7
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams338d ago0x99a918…ac3788
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams338d ago0xadc68f…0c977a
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams338d ago0xfac004…b5434e
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams338d ago0x0be93e…ab841c
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams338d ago0xcc4dda…1ab8fc
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams339d ago0x557e0e…fb7a70
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams340d ago0x7f5696…84bc8a
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams340d ago0x22543f…fbae5f
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams340d ago0xb5472b…fc6f92
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams340d ago0xf74399…ce9a30
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams340d ago0xbe2d20…193af0
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams340d ago0x288a46…0704d3
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams340d ago0xad3d22…4eb5aa
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams340d ago0x5e415a…c3f480
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams340d ago0x8f943e…1b8bf5
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams340d ago0x131834…5af439
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams340d ago0x1c142f…aefce4
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams341d ago0x79166e…f88d83
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams341d ago0x3b61d9…22200f
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams341d ago0x919d75…9ac51d
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams341d ago0x0d8c68…ee4c49
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams341d ago0x87a9db…2bb4f9

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.