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.00M Roundhouse has indexed across 1,401,091 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%daydreams344d ago0xea9a7e…f7ff35
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xb68415…0fafb5
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x3b5cf5…11725b
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xec496d…739a31
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x1f7aff…769f95
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x30683d…528e90
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x41afc9…b334fd
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x3b009a…c5a755
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x25540c…41b9a3
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x091b9a…944e60
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x288f95…a64f8f
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xce3b65…663c65
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x102d68…a1b9dc
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xf9c8fb…296cea
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x6ada9f…400cd1
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe8261b…4373ae
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x9ba62d…59ad64
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x9cc2e0…f68246
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xb8706f…04c252
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x4197e8…cf2532
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x8902d7…943f41
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x99650a…9ea55e
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0xe5c70a…7d1f2e
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x5c94b7…e15b07
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x44d4ff…0ce715

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.