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 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%daydreams344d ago0x179470…0952fb
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams344d ago0x27f4e2…51cf9b
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams344d ago0x7f2f10…e11c71
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams344d ago0xaaf682…19d215
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams344d ago0x861c39…00742c
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams344d ago0xacc243…1a44ec
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams344d ago0x462483…28f367
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams344d ago0x9e704d…446525
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams344d ago0x07b628…f4f6e4
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0x4cc7d3…7d4be1
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0x63e50e…29fa3b
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0x2fee2e…821dea
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0x1e45fd…39dc13
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0xb8dbf5…abc846
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0x43b0b6…c993a1
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0x09eba7…fb4a6c
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0xa2dc2c…edea6d
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0xfeb585…f3f9b5
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0xfc7ae2…0cd5e8
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0x714b77…f28e8b
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams345d ago0xd23497…9b7740
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams346d ago0xd290c2…0aa023
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams346d ago0x2a6b71…330e30
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams346d ago0x7b7ea0…e776ea
0x68b6…62170x6482…b779BaseBase$0.0001100%daydreams346d ago0x221155…9d18f3

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.