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%daydreams341d ago0xc4f55e…aa379f
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams342d ago0xf600e3…c34269
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x0b9c7c…e80926
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams342d ago0xb7cdf6…3f130f
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x87c55d…79a894
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x7e276d…680adf
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams342d ago0xf3e5b4…2cc4f6
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams342d ago0xdc0a01…104eeb
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams342d ago0xbc5e09…36c0e9
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x5e0c89…9ac550
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x3504eb…2fc9c2
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x21cbe3…146835
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x18a111…7ef42c
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xb52c64…d55714
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x8566a3…f8b9d3
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x25a69b…6062f4
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xfb53c5…eeeb96
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x74737e…a854f5
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xa65699…445d59
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x4e1a17…0ff0f7
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xbb8dd4…125563
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x3a1684…e505c2
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x6947b9…b9c2d3
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x2fb8ba…1aeb4f
0x6ada…c4cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x04bece…c15763

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.