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%daydreams343d ago0x4ab860…0e19b3
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xe8b510…a198e6
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xd4aedd…eab773
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x2a0f7c…9b6e9d
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x274e9c…e3bc39
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x3db5a8…9f0e4d
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x1c9a91…d4bc39
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x154736…9e7d2c
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xa1fa4b…78419e
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xb9cb55…4395c6
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x59bf76…d8d13f
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xe2987b…520a00
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xce8261…b9534a
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x2feb93…d310eb
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x676346…83dbcc
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x487277…cf7ae0
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x420bcb…b1fbda
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x89aa6f…c6a31c
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x918501…c52769
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xc8e829…7770d7
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x7863b5…26db5c
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x28a05f…716a88
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xe45e24…16b0c9
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x2faf0b…51c51e
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xc8d0a8…9cc44c

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.