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%daydreams343d ago0x82e13f…84382f
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams343d ago0x1d5aa5…f37665
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams343d ago0xee8986…e3c3ff
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams343d ago0x709f4c…474f6f
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams343d ago0x748b0e…efc50a
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams343d ago0x1d6fb1…1aec7c
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams344d ago0x8c9759…36d0a4
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams344d ago0xfe2b4b…248d10
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams344d ago0x3306d7…594646
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams344d ago0x1280ee…b0e27d
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams344d ago0xd7cbf2…4ef2fc
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams344d ago0xcbf2fe…135810
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams344d ago0x48974f…1265a4
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams344d ago0x17cf0b…3f3768
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams344d ago0x03d800…3a1a09
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams344d ago0x3da173…0b567f
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams344d ago0x374f1d…07d48d
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams345d ago0x19582f…e08009
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams345d ago0xc891cc…633262
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams345d ago0x065929…e0c1b4
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams345d ago0x3f875e…509d68
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams345d ago0xaba172…ea57c8
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams345d ago0x2a85a4…1b696d
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams345d ago0x09e3e8…27545b
0x0a84…34310x6482…b779BaseBase$0.0001100%daydreams345d ago0x9fd719…a0b5de

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.