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%daydreams343d ago0xfd44a3…81fa05
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams343d ago0x333a44…f3e770
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams344d ago0x93051c…a95733
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams344d ago0x8bc3dd…0c0720
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams344d ago0xcbf7d7…98878a
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams344d ago0xf55fa9…fc65ab
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams344d ago0xc1100a…8d7290
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams344d ago0x7efacf…664552
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams344d ago0x5c39c3…42e0c6
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams344d ago0x40eb41…85a307
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams344d ago0x616ec6…ad614c
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams344d ago0x67bbc6…f39f29
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams344d ago0xe209e8…b6500d
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams345d ago0x62d104…469a98
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams345d ago0x1b5506…4aa993
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams345d ago0x707d64…1a942b
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams345d ago0xa03022…dd12ba
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams345d ago0xb0c980…f9f007
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams345d ago0x30e8b3…405932
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams345d ago0x9028c1…d4800a
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams345d ago0xdc4eba…064efd
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams345d ago0x38fab2…42748b
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams345d ago0x846500…2ffc86
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams345d ago0x477ef2…4e7f9d
0x43b5…67df0x6482…b779BaseBase$0.0001100%daydreams346d ago0x4e1f7a…5ea8ba

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.