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 $3068.58M Roundhouse has indexed across 1,402,563 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%daydreams342d ago0x00442b…53680c
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams342d ago0x282988…caca3d
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams342d ago0x9ce815…d47206
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams342d ago0x513543…efcff6
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams342d ago0x888092…561a25
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams342d ago0xf1fe23…b3ae23
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams342d ago0x40dfab…95da75
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams342d ago0xbf6b07…33703c
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams342d ago0x2f77c4…01b5d7
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams342d ago0xdd17ff…8feb35
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0xf6ec69…64ee5e
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0xfa3a20…46282c
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0x82a5d1…f0a380
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0x95060e…2be6f0
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0x7c6bb8…e8399b
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0x9189c5…d42c09
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0x80bd88…bb9eb9
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0x813ca1…756853
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0x767d28…d3f4bc
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0xf6a285…a0faae
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0x54d5ec…22df90
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams343d ago0x52cc6b…09ef50
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams344d ago0xd117d3…bf6cc8
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams344d ago0xde4d98…ab38f7
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams344d ago0x0b3857…b12e95

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.