AgentReport

0x4bec…f549

0x4bec3d89abd5f4a45937bab11a0879527605f549Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
278
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.00M Roundhouse has indexed across 1,401,091 wallets — less than 0.0001% of it.

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

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

$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
    278 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.00278276d 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 278 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams345d ago0x890790…88e7f5
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams345d ago0x156ae5…944ce1
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams345d ago0xa8a462…b7e539
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams345d ago0x72e1be…ef354b
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams346d ago0x96c563…d3c320
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams346d ago0xc96904…2e96df
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams346d ago0xa08512…dc9c0a
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams346d ago0xd82750…6399aa
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams346d ago0x3db8f3…b232bb
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams346d ago0x2f035f…a30a23
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams346d ago0x570b67…580321
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams346d ago0x523d58…52ef3b
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams346d ago0xa0435d…830b43
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams346d ago0xd6baf7…3d9ab7
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams347d ago0x8071cc…6c2318
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams347d ago0x7f364f…2c853c
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams347d ago0x5a868d…a9ff80
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams347d ago0xfba10e…3f02a8
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams347d ago0xa95320…e2e019
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams347d ago0xd98972…a68daa
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams347d ago0x032e6e…642ded
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams348d ago0xc31e0f…46fe71
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams348d ago0x0d28ad…b93fe9
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams348d ago0x77369c…fda8ab
0x4bec…f5490x6482…b779BaseBase$0.0001100%daydreams348d ago0x357674…3f74b6

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

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

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: 0x4bec…f549

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