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 $3068.58M Roundhouse has indexed across 1,402,396 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%daydreams341d ago0x84ce07…18737a
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams341d ago0xd216f5…22b8e4
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams342d ago0xd26bca…6dd29f
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams342d ago0xd54bdb…4f32ab
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams342d ago0x4e1ea6…48bb06
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams342d ago0x7435f2…e4be3c
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams342d ago0x213008…e85d78
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams342d ago0xcae163…df2f5a
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams342d ago0xcc5964…712b53
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams342d ago0x57d0a3…52573a
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams342d ago0xbbfaf9…e25a9a
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams342d ago0x896be1…6eff2c
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams342d ago0xd5e767…b3c35d
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams343d ago0xb26af0…f9daaa
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams343d ago0x977458…bdc285
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams343d ago0x517459…3500cb
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams343d ago0x965e9e…95f81e
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams343d ago0xe5c90c…21b989
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams343d ago0xa2b92d…5b109e
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams343d ago0xfd79f7…a1e9a5
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams343d ago0xe7c729…3ed7dc
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams343d ago0xabca4b…d4a5c9
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams343d ago0x7dc536…2ad579
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams344d ago0xad839f…80e804
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams344d ago0x4eceda…eec672

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.