AgentReport

0xa222…effd

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

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

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

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

$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
    275 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.00275276d 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 275 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x63681e…e4b8a5
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x7c8c65…8d4813
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x56edfc…9082c2
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams346d ago0xa4383d…098a7e
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams346d ago0xd21296…a8cb77
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x95bb7c…3277fb
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams346d ago0xa83bfb…50178f
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams346d ago0xbc1ac1…c7d07c
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x66f07f…dd5e0d
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x0f4717…815daa
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x3037d4…c7e47d
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams347d ago0x2b01e4…5599ef
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams347d ago0x2597ce…2e36dd
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams347d ago0x1c17d7…111ae8
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams347d ago0x4f3ce4…84a5ad
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams347d ago0x292d33…f1cc01
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams347d ago0x6f492f…ed65ee
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams347d ago0xf5d0c1…9697b1
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams348d ago0x6567a0…9744b2
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams348d ago0xcda437…b6678d
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams348d ago0x0e2039…6491ec
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams348d ago0x9224d0…e86253
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams348d ago0x9e4850…d5b53b
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams348d ago0x9d1160…ae505c
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams348d ago0x863b29…bf49bc

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

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

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: 0xa222…effd

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