AgentReport

0x6ada…c4cd

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

Paid $0.03 of the $3067.25M Roundhouse has indexed across 1,401,192 wallets — less than 0.0001% of it.

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

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

$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
    257 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.00257276d 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 257 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams349d ago0xc63086…97dec5
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams349d ago0xaa9823…23711b
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams350d ago0xff34fb…6538fb
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams350d ago0x50169d…f909d7
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams350d ago0x957333…2c9ada
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams350d ago0x0c1245…a6152a
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0xa02614…da4262
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0xfa88fc…cea6f2
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0x42ce7d…a8aabf
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0x192334…9d5278
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0x214076…2b2658
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams351d ago0x20685b…81a49b
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0xbada95…7c8da3
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0x6b054a…5627fd
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0x264be2…f5cc98
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0x7e10db…5f7f26
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0xd6fc7d…813ba5
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0x2831fd…2805a1
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0xa614a9…3a36df
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0x7dc202…343c7c
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams352d ago0x6605fb…4f41b6
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams353d ago0x7b981c…fd92be
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams353d ago0x2c8eec…931962
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams353d ago0x153f8d…043a5e
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams353d ago0xedea28…4aa236

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

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

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: 0x6ada…c4cd

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