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,396 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 276d 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.00252276d 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%daydreams338d ago0xaf132b…c86f4a
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams338d ago0x6f4bce…2be8ff
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams338d ago0xa585a1…f202f9
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams339d ago0x290986…640a3c
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams340d ago0xc89ac2…c63f02
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams340d ago0x047906…16454b
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams340d ago0xa2588a…12d859
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams340d ago0xe1fbb2…16e578
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams340d ago0xef623a…346d75
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams340d ago0x95c589…e408b4
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams340d ago0x669d3c…06539a
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams340d ago0xc5c257…63834a
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams340d ago0x77f6ea…99b083
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams340d ago0xce7813…589a12
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams340d ago0xf68d96…f361da
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams341d ago0x4e5d28…d1206c
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams341d ago0xec9334…a8be78
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams341d ago0x3c4804…059483
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams341d ago0x74bc33…eb85b7
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams341d ago0x6616e5…6f9ade
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams341d ago0x98b176…6b07cc
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams341d ago0xda69c2…66be1a
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams341d ago0xa6e2b7…c59eb5
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams341d ago0x1157a2…8c3e7a
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams341d ago0xa6f048…6d726a

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.