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%daydreams337d ago0x8ab3a8…9e22f8
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams337d ago0xc6652d…edf30a
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams337d ago0x464ceb…b13cfa
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams338d ago0xd9bb71…f41853
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams338d ago0x189539…988023
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams338d ago0xae7082…61edf4
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams338d ago0xbbd59e…551512
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams338d ago0xc94d72…21c4f2
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams339d ago0xe162b8…842a09
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams339d ago0x53d634…bc59a5
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams339d ago0xf55a09…36d708
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams339d ago0x57ed0d…a9c914
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams339d ago0x59a4fa…da7a41
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams340d ago0xe87416…43eb21
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams340d ago0xd3fcb5…9a3672
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams340d ago0x825b2d…a103bb
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams340d ago0xf179e8…3d41b2
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams340d ago0x887e9d…2d4066
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams340d ago0x8ca71b…094987
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams340d ago0xf835d7…c05666
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams340d ago0x097bb8…6a5e8b
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams340d ago0x31bdc6…79c89e
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams340d ago0x5865a9…f7f9a4
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams341d ago0x489551…30ac61
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams341d ago0x348b4a…0ef6ce

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.