AgentReport

0x0621…46c4

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

Paid $0.03 of the $3070.29M Roundhouse has indexed across 1,403,290 wallets — less than 0.0001% of it.

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

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

$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
    256 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.00256277d 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 256 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams344d ago0xdd1def…a3b05f
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams344d ago0xa7f4b2…b18766
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams344d ago0x6505f6…561b99
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams344d ago0xf8c83e…267259
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams344d ago0x83bfb6…10fc71
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams344d ago0x1fe18c…960f40
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams344d ago0x161ca2…66c486
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams345d ago0xfe7bd6…b7af83
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams345d ago0x57dbed…2bf73a
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams345d ago0xa41362…eea878
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams345d ago0xb1b9ea…146555
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams345d ago0xbff95e…557c31
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams345d ago0xc681c1…c3b678
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams345d ago0x708abf…c8b39c
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams345d ago0xbf7e85…8473b0
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams345d ago0x65aa8c…f71afb
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams345d ago0x3f57c0…eeb95d
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams345d ago0x151e0e…d1829d
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams346d ago0xf8e304…486105
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams346d ago0xa4c8e9…d067c7
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams346d ago0x58a8af…899d32
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams346d ago0xdee12d…73ed9e
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams346d ago0x1afa75…2bc7c8
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams346d ago0x337bdc…ad3f3e
0x0621…46c40x6482…b779BaseBase$0.0001100%daydreams346d ago0xda5cd4…fe82d9

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

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

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: 0x0621…46c4

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