AgentReport

0x1781…0973

0x1781d80a3c918f24ba7df45b304fb26dc2170973Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
252
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (252)

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.032521

$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 277d ago
    $0.03
    252 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.00252277d 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 252 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams349d ago0xd956d2…8d8b1b
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams350d ago0xd976e0…bd21fe
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams350d ago0x0658f1…d5e3e7
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams350d ago0x9d78d0…caa3e8
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams350d ago0x3e0804…67bea8
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams351d ago0xb9f06b…ad5c82
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams351d ago0xe6fe0c…e06411
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams351d ago0xfcc728…f2f1a2
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams351d ago0x2285bb…1aeb27
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams351d ago0x1e91ad…fb228f
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams351d ago0x7527f1…7668b9
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams352d ago0xb8337e…bbaf55
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams352d ago0xd6e9bd…1d4a03
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams352d ago0xf133e1…656eaa
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams352d ago0x896d2a…3c155d
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams352d ago0x87b742…3a222e
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams352d ago0x987720…c8d932
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams352d ago0x99de9a…981bab
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams352d ago0x23369d…9bb8d4
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams353d ago0x0bc817…d0a167
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams353d ago0xc6dc98…b92503
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams353d ago0xcdb69a…dd6589
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams353d ago0x36864e…3e9a9c
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams353d ago0x9a7776…a76f93
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams353d ago0x42d022…015a32

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 0x1781…0973 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x1781d80a3c918f24ba7df45b304fb26dc2170973

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: 0x1781…0973

curl -s 'https://api.roundhouseai.io/v0/agents/0x1781d80a3c918f24ba7df45b304fb26dc2170973'
curl -s 'https://api.roundhouseai.io/v0/entities/0x1781d80a3c918f24ba7df45b304fb26dc2170973/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.