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.43M Roundhouse has indexed across 1,401,367 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%daydreams352d ago0x63a8b6…f2d817
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams352d ago0xb60634…45ffef
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams353d ago0xfd5882…881c2a
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams353d ago0x2e9704…98e0f1
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams353d ago0xc170eb…e1de2d
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams353d ago0x8e7579…2aaa01
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams353d ago0x71946b…29048c
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams353d ago0xdd2708…9341c2
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams354d ago0x9a4bd1…5a6f7b
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams354d ago0x11beae…bf3481
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams354d ago0xba25a5…58a590
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams355d ago0xb19726…d80208
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams355d ago0x870eb3…948187
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams355d ago0xd6a5f0…cc8d73
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams355d ago0xe59acd…3e8455
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams355d ago0x887a79…da7ccb
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams355d ago0x6b03da…794f9c
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams356d ago0x7dd2ff…2f3d45
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams356d ago0x5a6b9e…c7261e
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams356d ago0x9be9e2…fc35ac
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams356d ago0x8c44ff…a85df9
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams356d ago0xfdf1f6…dc51e9
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams356d ago0x8ca6a5…052453
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams357d ago0xc78f49…8eb95c
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams357d ago0x2e76a8…b7fc9b

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.