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,401,091 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%daydreams341d ago0xcd8ae7…e06974
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams341d ago0xf17795…e00ea6
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams341d ago0x02bf58…4cbada
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams341d ago0xe82519…07e966
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams341d ago0x02de95…a7d6ab
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams341d ago0xf15184…b28c75
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams341d ago0xf6df53…3a7c98
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams341d ago0x0a0294…f84d05
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams341d ago0x4ec060…7e098d
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams342d ago0x85b939…1ecf1d
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams342d ago0x6e05cc…b19de4
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams342d ago0xbedd6d…b7f977
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams342d ago0xa10728…373d56
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams342d ago0xc63441…a15a9f
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams342d ago0xf6c284…5fdad9
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams342d ago0xae527a…bbd108
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams342d ago0xf5faa1…3e0e0c
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams342d ago0x143138…a6fc72
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams342d ago0x0e435e…6da20a
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams343d ago0x2dcbf0…04292a
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams343d ago0x6a8eb2…d668e0
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams343d ago0xcff3cc…34f431
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams343d ago0x000c51…2c8ed2
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams343d ago0xea35e3…f1755f
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams343d ago0x749466…764875

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.