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%daydreams323d ago0x4b7ada…43656a
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams323d ago0xb4455c…1856c2
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams323d ago0xcd9593…94140c
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0xa9b50d…1e0bf7
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0x75b442…02cc75
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0xe610a4…d9671d
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0x495c12…7e6e6b
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0xfe7e21…3d6589
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0xa7baa0…ff1088
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0xd574b2…6c3fea
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0x841188…c2e928
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0x062aa3…1b6d1c
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0x00f03a…7bf772
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0x60f45c…1598d9
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams324d ago0xedf33a…2b1686
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams325d ago0x6d7b3c…6006fe
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams325d ago0x45fe37…809ec8
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams325d ago0x077bab…9528b1
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams325d ago0xcc44ad…8aeb92
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams325d ago0x7ba0f8…39c310
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams325d ago0x0be02b…9eebe0
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams325d ago0xca9e9f…631d7b
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams325d ago0x638397…1ec7c5
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams325d ago0x4cf8da…50d058
0xa222…effd0x6482…b779BaseBase$0.0001100%daydreams325d ago0x19e409…1e9342

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.