AgentReport

0x8620…83c9

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

Paid $0.03 of the $3103.01M Roundhouse has indexed across 1,404,332 wallets — less than 0.0001% of it.

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

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

$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 277d ago
    $0.03
    260 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.00260277d 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 260 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams344d ago0x75a96a…09fef1
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams344d ago0x039d36…ad0ed2
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams344d ago0x61e61a…0be745
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams344d ago0x4a82fd…1097b5
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams344d ago0x73bc6d…c50e73
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams344d ago0x5e3b4d…368fa8
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams344d ago0x53a885…351243
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams345d ago0x98828e…4f73a4
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams345d ago0xc89af7…8b4381
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams345d ago0x992f5c…40cbaf
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams345d ago0x3b86ea…5b6a2d
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams345d ago0x31f64c…3a3001
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams345d ago0x486fe3…19e8ee
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams345d ago0x4357aa…da3ae4
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams345d ago0x2dcaf4…cf1168
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams345d ago0xc30d8b…308583
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams345d ago0x2c2572…34c677
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams345d ago0x4a1c97…dc5257
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams346d ago0x8eb095…6efe48
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams346d ago0xa23149…49f26b
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams346d ago0xf6b0b4…e4c591
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams346d ago0x7c9fff…ad4d9c
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams346d ago0x3c2c76…ff80f7
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams346d ago0x7dbceb…01f599
0x8620…83c90x6482…b779BaseBase$0.0001100%daydreams346d ago0x37da7c…30a6ca

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

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

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: 0x8620…83c9

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