AgentReport

0x877f…a94d

0x877fed895a4fe486ec83350b4de5d06a9d8aa94dExplorer
Paid out
$0.02
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
246
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.02 of the $3067.00M Roundhouse has indexed across 1,400,982 wallets — less than 0.0001% of it.

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

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

$0.02 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.02
    246 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.02$0.00246276d 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 246 observed settlements.

Organic volume $0.02 of $0.02 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams349d ago0x98b72d…be02f1
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams349d ago0x48fd89…45b6fe
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams349d ago0xbe962a…776af3
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams349d ago0xe38088…ee9ff4
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams350d ago0x5aea2d…4e4a3c
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams350d ago0x84f0eb…776d82
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams350d ago0x16e3fa…d0cc32
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams351d ago0x8e9053…709f01
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams351d ago0x4f9441…3988ed
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams351d ago0xe7d1e0…c26571
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams351d ago0x8d69e5…3d822c
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams351d ago0x1aec82…079f45
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams351d ago0xa6500b…6d33c4
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams351d ago0x15c740…441c69
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams351d ago0x7e1255…985d68
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x0264a1…6a67e6
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams352d ago0xcc3a8e…0a4d16
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams352d ago0xe9e38a…3c1d38
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x819b07…23828a
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams352d ago0xab68f3…d4ae60
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x5095cc…912f39
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x263196…05dbc7
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x943fd0…dee299
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams352d ago0xc9d9da…c43350
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams352d ago0x52f42a…c7283b

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

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

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: 0x877f…a94d

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