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%daydreams337d ago0x4c3b80…2d3ef9
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams337d ago0xd97641…636819
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x141dcd…c44409
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x0626de…d26ec0
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams338d ago0xc0944c…fab875
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams338d ago0xa95583…c1f092
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams338d ago0xa0ea49…62a264
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x33c376…b7ce40
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams338d ago0xb02e28…f8032d
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams338d ago0x6079bd…f8d2f7
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams339d ago0xd61632…9f0b6b
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams339d ago0x534105…3679d6
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams339d ago0x128e33…5f4074
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x26c0ed…42dfc0
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams340d ago0xb05794…57a487
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe790b1…05d0e9
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x375d4d…479fd4
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x25f8dc…3740d2
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x16cef2…1f8f00
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x8c34a6…9258ab
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x322714…89d2c1
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x2f10ee…fd911f
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe723e3…198b68
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams340d ago0x21b299…93c9c7
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams341d ago0x7b6956…068b0a

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.