AgentReport

0x43b5…67df

0x43b5149cf4f4090bbb1b8cb61c5d564a7db867dfExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
260
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,563 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (260)

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.032601

$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
    260 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.00260277d 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 260 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams348d ago0x487ffc…660c9a
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams348d ago0x6f37d5…5860fa
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams348d ago0xa02b33…41c564
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams349d ago0xf65e16…570d8f
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams349d ago0xd5fa47…479a2d
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams349d ago0x38e429…afd202
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams349d ago0xa18e90…b5bd58
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams349d ago0x8a636c…c14f03
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams349d ago0xcc7f82…aeb510
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams349d ago0x35caae…ba7e12
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams350d ago0x12d0d4…0bf040
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams350d ago0xe13e7b…9550d0
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams350d ago0xcd5a14…d153af
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams351d ago0xabd458…4b63b5
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams351d ago0xfc4607…9bc947
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams351d ago0x45d4f7…108f51
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams351d ago0xa3f4a3…55658a
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams351d ago0xaf07a1…a079ea
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams351d ago0xb501a9…7f56a8
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams351d ago0x077fc0…0e4135
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams352d ago0x618113…f8c462
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams352d ago0x711c6a…888385
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams352d ago0x655ea7…b99023
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams352d ago0xf35101…5401cd
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams352d ago0xb69bfc…93ec2b

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 0x43b5…67df has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x43b5149cf4f4090bbb1b8cb61c5d564a7db867df

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: 0x43b5…67df

curl -s 'https://api.roundhouseai.io/v0/agents/0x43b5149cf4f4090bbb1b8cb61c5d564a7db867df'
curl -s 'https://api.roundhouseai.io/v0/entities/0x43b5149cf4f4090bbb1b8cb61c5d564a7db867df/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.