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.43M Roundhouse has indexed across 1,401,742 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%daydreams341d ago0x35a8b3…98d2ba
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x6a5ac8…5bc350
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x0ded94…31c2ff
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x3e6319…770609
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x3bc67b…6c429d
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x43d3eb…7cdd04
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams341d ago0xe9b726…a683cd
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x70c4f9…af1292
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x5d5d04…f20eff
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams342d ago0xedb2f7…1f5471
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams342d ago0xd863d0…fed8ec
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x291311…26ba3a
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x74e5f0…5793b8
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams342d ago0xbb3f61…0f2e2c
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x2fa532…33d4ad
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x2e5d94…95a09f
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x0ede56…ab5948
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams342d ago0x9d6829…9669c1
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x0bc9bb…2fbc45
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xb1685f…6e5533
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x2ba4e6…e8fce4
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x7ff725…f2f99f
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xc83484…29a2f2
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xe15664…0f3627
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x0eaf98…f711f8

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.