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,722 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%daydreams346d ago0xc84dcc…553382
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams346d ago0x46e2ad…d58e14
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams346d ago0xf010dd…811b2a
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams346d ago0x5d30bc…e08ab4
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams347d ago0xb50178…a7edc9
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams347d ago0x21cdc4…634a99
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams347d ago0xa45a87…c1557e
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams347d ago0x4321d4…ced304
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams347d ago0x8bfd09…a5fba3
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams347d ago0x459d1a…1915bc
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams348d ago0x316f3d…b8b654
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams348d ago0xc22926…c7339f
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams348d ago0x054fb6…04edb7
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams348d ago0x08691a…317f38
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams348d ago0xfe2ab6…dbf93b
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams348d ago0x1f3b4d…70cbe4
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams348d ago0x471e31…915f72
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams348d ago0x2dfde2…5075dd
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams348d ago0x75ef27…37d8a1
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams348d ago0xe155c9…f6ea89
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams349d ago0x407272…333eeb
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams349d ago0xbcaea4…78e8bb
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams349d ago0x690463…ec278b
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams349d ago0xc5e48a…3c7c13
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams349d ago0xe407c8…316788

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.