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.43M Roundhouse has indexed across 1,401,367 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%daydreams354d ago0x3cd714…5e9aeb
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams355d ago0xad3af6…7ab39b
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams356d ago0x61bb75…4019f1
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams356d ago0xf88e92…51c2fe
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams356d ago0x48c2b2…8f12a4
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams356d ago0xc7595c…c84549
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams356d ago0xd704ae…e07de9
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams356d ago0x9caf2b…00bc06
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams357d ago0x5c5ff5…07e650
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams357d ago0xeeb6eb…84000f
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams357d ago0xd29a0a…c90008
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams357d ago0x2b1230…d91d15
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams357d ago0xe7bc93…85f819
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams358d ago0x3dc9b1…52f689
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams358d ago0xfabfbd…9a6ce7
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams358d ago0xb1d20e…b8ccef
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams358d ago0xd3d6d1…352d80
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams359d ago0xeb6451…9d402d
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams359d ago0xc8b8e3…944271
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams359d ago0x18f8fc…ce0763
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams359d ago0x8e961b…d175a4
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams359d ago0x33ebfa…11de99
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams359d ago0xbede48…a80879
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams360d ago0xd6c9ac…93aa60
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams361d ago0x702a16…2806b2

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.