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,563 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 277d 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.00261277d 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%daydreams353d ago0x9d9d5a…e719bd
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams353d ago0xa0329c…33b1d0
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams353d ago0x6fe4e3…0c8f9e
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams353d ago0x38521b…077780
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams353d ago0xc55abf…c2e59a
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams354d ago0x7affe7…b49fd5
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams355d ago0xf4c1be…c134fa
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams355d ago0x99c099…110117
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams355d ago0x88b404…caaca6
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams355d ago0x9d330c…b187c1
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams356d ago0xb11032…13b1be
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams356d ago0xb38b3c…f83cd6
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams356d ago0x11e8a5…914c4f
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams356d ago0x6188fb…3f0c51
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams356d ago0x5bb398…b031e4
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams356d ago0x73b857…509169
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams357d ago0x488775…1a5f6c
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams357d ago0x14886d…30c212
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams357d ago0x47772b…131448
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams357d ago0xcbc1c5…9ff3d8
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams357d ago0x209463…019271
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams358d ago0xb6289d…5136b4
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams358d ago0x0cfea6…db1508
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams358d ago0x14759a…a0273c
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams359d ago0x33e961…36fcec

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.