AgentReport

0xb6fb…7d1e

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

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

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

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

$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
    252 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.00252276d 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 252 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams326d ago0x70beed…f70d02
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams326d ago0x9a13c0…d6d418
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams326d ago0x027460…61552a
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams326d ago0xb7f639…f222c1
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams326d ago0x3ec8cb…5478b5
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams326d ago0xd6200d…58a9b1
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams326d ago0xe6a9de…6ced17
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams326d ago0x686a9d…2939ac
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams326d ago0xd51a58…60eb39
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams327d ago0x52991b…c8a759
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams327d ago0xef1f85…177b22
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams327d ago0x9b2c27…2e4e9e
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams327d ago0xe6c9ed…d7476c
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams327d ago0x77ba4e…25a85d
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams327d ago0xcbd32f…076d7b
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams327d ago0xff435c…5db421
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams327d ago0x2e6f02…c26354
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams328d ago0xcc7eca…7c6cf2
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams328d ago0x824a75…0a8844
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams328d ago0xa46d30…19ec6b
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams335d ago0xb3d354…328b25
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams337d ago0xcade20…2b3cfe
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams337d ago0xbe73db…73400a
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams337d ago0xadcb59…a427e4
0xb6fb…7d1e0x6482…b779BaseBase$0.0001100%daydreams337d ago0xdb4978…468eac

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

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

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: 0xb6fb…7d1e

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