AgentReport

0x0a84…3431

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

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

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

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

$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
    268 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.00268276d 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 268 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams348d ago0xc3551e…efc5d6
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams348d ago0xb467dd…35830e
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams348d ago0x9c225e…6510bc
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams348d ago0x5d4dd1…eac0ce
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams348d ago0x639ca0…70b596
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams348d ago0x66e333…541e54
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams348d ago0xf3983c…ca1bab
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams349d ago0xe6d2f6…82fec1
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams350d ago0xae5965…a6fcdc
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams350d ago0x44ec54…f57521
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams350d ago0x00e6dd…ff9a6f
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams350d ago0x127ad6…78da34
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams350d ago0x77215d…e036d6
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams351d ago0x5f626c…c14cd9
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams351d ago0xf80be9…228c37
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams351d ago0x7b2066…79ca9a
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams351d ago0x1a41cd…92df3c
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams351d ago0xfa838a…c4ef70
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams351d ago0x2779b1…5e0633
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams352d ago0x6e9c99…47cad4
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams352d ago0x92b00e…472548
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams352d ago0x588bae…a1af81
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams352d ago0xd6e312…c19433
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams352d ago0x5aad72…17d7c4
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams352d ago0xe452a3…5d520e

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

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

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: 0x0a84…3431

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