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%daydreams326d ago0x05dff7…688801
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams326d ago0x09c30d…21228c
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams326d ago0x8cc16d…c60e67
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams326d ago0x77ecb8…1a33eb
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams326d ago0x2fafdc…8cd26c
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams326d ago0x27911f…7d72e4
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams326d ago0x470273…deb449
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams327d ago0xd112e7…8fb356
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams327d ago0x3e6321…833657
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams327d ago0xabfe02…cfbff2
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams327d ago0x326a33…caf1db
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams327d ago0xb539ff…114272
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams327d ago0x003d3c…3f0610
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams327d ago0xb5eeef…436f16
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams327d ago0xf375a3…8ed6c0
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams328d ago0xab465b…628a32
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams328d ago0x06efe7…11d35c
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams328d ago0xc6ae1c…f5f49b
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams328d ago0x9d8575…4de26a
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams328d ago0xc380ce…09eac5
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams336d ago0xa45d3b…fd0444
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams337d ago0xde63b4…232553
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams337d ago0xe7bf05…1f9ac3
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams337d ago0x1d03d7…8a6297
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams337d ago0xf5f5d0…ac6690

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.