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 $3067.84M Roundhouse has indexed across 1,402,228 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%daydreams326d ago0x16aaba…33c1bc
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams326d ago0x92d03a…69a6aa
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams326d ago0x1bbbc6…aa6b41
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams326d ago0x9a8937…dd5505
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams327d ago0x1231ea…8f2750
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams327d ago0x606a78…51f9d5
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams327d ago0xef19a5…8059fb
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams327d ago0x519ac8…ea6345
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams327d ago0x39f667…1f18f9
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams327d ago0xd689c0…3dbf4f
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams327d ago0x43f3bd…bc213f
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams328d ago0xbb19d1…4cf0d6
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams328d ago0x7e26ce…847a4b
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams328d ago0xe91887…7d52ce
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams328d ago0xe02ee6…d0c8f6
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams328d ago0x909e1e…7ed566
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams336d ago0xd00881…77d585
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams337d ago0x32613d…13b49d
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams337d ago0xe6a1e3…a881b6
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams337d ago0x3edf14…944c0b
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams337d ago0xd12ede…866d59
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams338d ago0x0b3dff…6c4f8b
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams338d ago0xb24c91…a027d0
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams338d ago0x4f05c2…024d2a
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams338d ago0xd37026…bc7503

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.