AgentReport

0x68b6…6217

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

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

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

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

$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
    261 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.00261276d 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 261 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams323d ago0xd08ee9…e8dc7d
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams324d ago0x34d57b…03cef9
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams324d ago0x881914…556332
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams324d ago0xf0fc8b…1266c1
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams324d ago0xd5d347…ab1400
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams324d ago0x6c6303…f0572e
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams324d ago0xb18d76…6570b8
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams324d ago0x2129fa…0fa0a0
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams324d ago0xe2f867…4e75ff
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams324d ago0x2b9429…1105c7
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams324d ago0xeb5967…fd3324
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams325d ago0xbf35ef…9e0628
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams325d ago0x332823…966939
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams325d ago0x8dce70…6e212d
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams325d ago0x55530e…9c01e8
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams325d ago0xae5890…099a4b
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams325d ago0xb5cf32…c753a6
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams325d ago0xe3f248…c26c6a
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams325d ago0x295ec1…f64596
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams325d ago0x72a496…4205ce
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams325d ago0x165990…082df7
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams325d ago0x52542e…40b6e7
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams326d ago0xfafdd3…e724b8
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams326d ago0x4fd280…951f49
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams326d ago0xb490dc…5ac32a

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

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

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: 0x68b6…6217

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