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%daydreams344d ago0x10242c…280377
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams344d ago0x0bee78…8ce8ce
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams344d ago0x49bd96…623b39
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams344d ago0xdfa8c2…00336d
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams344d ago0x48a965…ef814c
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams344d ago0x5641f5…dc9148
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0x6f8dc3…c7a737
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0x922632…3f3c70
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0x29d606…7d2f0a
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0xacfd3c…6ecfdd
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0xf6d9d4…60efc2
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0xe72048…954886
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0xa18489…952592
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0xe64369…3e8c70
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0x61f633…3ce90a
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0x4814e3…769a19
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0x673f7d…654296
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams345d ago0x720e0c…94a83c
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams346d ago0x19c3dd…82ab21
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams346d ago0x14699a…2f6acd
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams346d ago0x75ae84…171a49
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams346d ago0xac565f…71b451
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams346d ago0x5c6322…256172
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams346d ago0x6774f2…f6476e
0x1781…09730x6482…b779BaseBase$0.0001100%daydreams346d ago0xee0430…e79593

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.