AgentReport

0xe902…076d

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

Paid $0.03 of the $3067.00M Roundhouse has indexed across 1,401,091 wallets — less than 0.0001% of it.

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

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.032831

$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
    283 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.00283276d 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 283 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams337d ago0x7fec13…fdb091
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams337d ago0x9d4eb1…12b287
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams337d ago0x764812…2cfab4
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams337d ago0x11a281…09d9cb
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams338d ago0xfaa2ab…c0d412
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams338d ago0x5532e4…e585bf
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams338d ago0xaf99bd…b882e8
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams338d ago0x65d7a0…681920
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams338d ago0x12fcdf…887636
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams339d ago0xc69986…610fc6
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams339d ago0xcdb780…3a2319
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams339d ago0x79ebf9…e6b8e6
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams339d ago0x4caac8…52c9ea
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams339d ago0xe60d1a…ba5354
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams339d ago0x108fc3…1102df
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams340d ago0xd23857…edb9b1
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa09e76…6ff3ea
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x8897ee…1f70bd
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x22c976…a0d807
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x97d81c…256419
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x3f93a4…3e5ddf
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x1d8f58…2b2ca1
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x227005…e1ca6a
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x9b2cd8…974a01
0xe902…076d0x6482…b779BaseBase$0.0001100%daydreams340d ago0x771946…622e56

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

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

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: 0xe902…076d

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