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%daydreams341d ago0xad6a92…ede684
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams341d ago0x70e782…971c2d
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams341d ago0xd97940…7f1ad1
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams341d ago0x4c5655…34fa0b
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams341d ago0xdefcd7…5a9b60
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams341d ago0xed8e45…cae630
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0x07cc5b…af9f15
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0x64ea94…35bf91
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0x942c5e…4f53b1
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0xd098b3…0b8cf1
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0xde6e26…4efa89
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0x9e52bd…5c93dc
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0xc0eb2f…a0274b
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0x892091…161f35
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0x58d20a…adb5f0
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0xb79f84…f8e2b7
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0x0cff9b…6e8982
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams342d ago0xb85fe0…89dd58
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams343d ago0x7a4503…c7578e
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams343d ago0xbbd69b…87a388
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams343d ago0xcd0bfc…aa1e54
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams343d ago0x2810c9…c90152
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams343d ago0xb36893…9a5230
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams343d ago0xd22cf7…2a0040
0xe13d…f5420x6482…b779BaseBase$0.0001100%daydreams343d ago0x3f08f7…f02233

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.