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.00M Roundhouse has indexed across 1,400,982 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%daydreams326d ago0xd0a744…c4d01c
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams326d ago0x505159…6f675c
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams326d ago0x3ad028…9fe04d
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams326d ago0x486b55…d633e8
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams326d ago0x36e18e…2bae91
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams326d ago0xa3fc29…446747
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams326d ago0x23155b…9ba82c
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams326d ago0xbedd3f…f54c7f
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams326d ago0x2f37c0…bb9a8e
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams327d ago0x372248…432b30
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams327d ago0xdf57f8…2c2e7e
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams327d ago0xbfc631…e228b7
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams327d ago0x7124f5…d7c81d
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams327d ago0x48e63c…322107
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams327d ago0x634f9a…95d763
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams327d ago0x24fff1…80f9e4
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams327d ago0x67f8c8…c01866
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams328d ago0xd88f14…e93915
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams328d ago0x78f732…41a4a0
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams335d ago0x3f1c79…c37ac5
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams335d ago0xad1528…7dbeb7
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams337d ago0xea8a6c…3d9dfb
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams337d ago0xa38829…5ecc05
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams337d ago0x248368…1dc39f
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams337d ago0xbea3d7…17c29b

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.