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%daydreams353d ago0xe3653e…6696b1
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams353d ago0xe212e7…f2ca6b
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams353d ago0x58c0e7…cdb437
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams354d ago0x91cbdd…fe16c6
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams354d ago0xea4cb2…53f89e
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams355d ago0x1fbdbe…b2fbd2
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams355d ago0xa0b68d…1e4f7b
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams355d ago0x44db30…f5dffc
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams355d ago0xa21b9c…bf4545
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams355d ago0x987156…92971e
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams356d ago0x64e52e…6e18b0
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams356d ago0x553722…4844f0
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams357d ago0x234d4e…d84d72
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams357d ago0x7bde7c…557afb
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams357d ago0x2a2c26…3501be
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams357d ago0x26a249…c36401
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams357d ago0x86cd93…aa6692
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams357d ago0x6d1b0a…bedd20
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams357d ago0x6d70fc…6ffc75
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams358d ago0x923f02…982d37
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams358d ago0x6ae3fe…b14037
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams358d ago0x13122e…be6d41
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams359d ago0xf74173…873e02
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams359d ago0x30be54…f5aead
0x877f…a94d0x6482…b779BaseBase$0.0001100%daydreams359d ago0x3e9a40…200c71

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.