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%daydreams326d ago0x4ad153…81919d
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams326d ago0x6b3fe7…02b96d
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams326d ago0x151548…d40347
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams326d ago0x4ed80e…95ae32
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams326d ago0xd23cf6…dd23b0
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams326d ago0xb4df90…3fae33
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams326d ago0x61a45d…315ad3
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams327d ago0xd2980b…d5e646
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams327d ago0x596ed5…688913
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams327d ago0x48176e…5d0af8
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams327d ago0x7ac16c…e82efe
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams327d ago0xd351c6…a36fb4
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams327d ago0x46ba97…93dc23
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams327d ago0xcc76d2…7cafde
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams328d ago0xa48725…938421
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams328d ago0x01e6c1…a661bd
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams328d ago0x186f0f…1b4176
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams328d ago0x364b18…d967bc
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams336d ago0x832997…642f74
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams337d ago0xab57aa…ed1cec
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams337d ago0xd6b424…6f24d0
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams337d ago0x9f2279…e6ebe4
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams337d ago0x467a59…a81e71
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams338d ago0xa6c4fa…934bf5
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams338d ago0xd791ba…c8866e

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.