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,396 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 276d 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.00260276d 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%daydreams338d ago0x211482…9ef5b1
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams338d ago0x35078a…a23f49
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams338d ago0x6274d0…be0e67
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams338d ago0x774e86…2ecd05
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams338d ago0x42e62e…0d6a51
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams338d ago0x53bb4e…e65a96
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams338d ago0x9277db…85a8ec
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams338d ago0x228749…3f5876
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams338d ago0xd7a58b…523856
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams339d ago0x1e7e5d…003bba
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams340d ago0x0db278…eb9d46
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams340d ago0x57628a…7a951c
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams340d ago0x6977c3…be2e62
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams340d ago0x0f928d…c59bdf
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams340d ago0xe1072a…0c6cb0
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams340d ago0x0d6c4e…030ab3
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams340d ago0xc2a895…b22051
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams340d ago0xef0976…0e9a44
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa65abb…37e4e9
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams340d ago0xa43525…6f7159
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams340d ago0xf74ebe…780997
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams341d ago0x2e1363…3c0d65
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams341d ago0x470120…430a46
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams341d ago0xb96868…346341
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams341d ago0xc372a9…94398b

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.