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%daydreams353d ago0xc1d4da…5f42bd
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams353d ago0x01d96f…d8f901
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams353d ago0xfd9fd8…9180b7
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams354d ago0x1922df…237cbd
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams354d ago0x7619e6…ac749f
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams355d ago0x44e10e…dae0a9
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams356d ago0x6b1a6f…17d791
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams356d ago0xac57c1…ee76ba
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams356d ago0x9ebe92…0ddca4
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams356d ago0x44f1f0…462f69
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams357d ago0x0aa844…9fe723
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams357d ago0xc8dabd…621f95
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams357d ago0x3079df…060459
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams358d ago0xe6cb9d…c60ea4
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams358d ago0x820954…420886
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams358d ago0x9f2217…ae5d00
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams359d ago0x35c046…a4d258
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams359d ago0x98027e…0e6d19
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams359d ago0x81e5d2…b5cf81
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams359d ago0xe6959b…713626
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams359d ago0xded6c7…bb3a97
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams359d ago0x227b15…d62dd0
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams360d ago0x7c3c8e…6223de
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams361d ago0x79e608…2b2d41
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams361d ago0x4e6925…f78253

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.