AgentReport

0x244b…dddd

0x244b27c104faa9922ba72bd475b36ce6c75dddddExplorer
Paid out
$991.20↓ 100%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
74↓ 100%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $991.20 of the $3063.39M Roundhouse has indexed across 1,398,970 wallets — less than 0.0001% of it.

Chains (from the recent scan): Ethereum (74)

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%$991.20741

$991.20 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.

  • 0x5c7b…35c5 · last paid 12d ago
    $991.20
    74 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
0x5c7b…35c5$991.20$0.007412d 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 74 observed settlements.

Organic volume $991.20 of $991.20 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d12d ago0xe3aa11…6ae6a6
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a12d ago0xedd1ed…4912e1
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de14d ago0xd1f017…5bb92f
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d14d ago0x94d7f8…17a536
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d15d ago0x9c7305…b419a3
0x244b…dddd0x5c7b…35c5EthereumEthereum$21.0070%0xc10a…ae5d15d ago0x96fb07…780a5f
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d17d ago0x4b540a…f0bbad
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a17d ago0xe6a362…fd871a
0x244b…dddd0x5c7b…35c5EthereumEthereum$13.6570%0xd016…b67a18d ago0xda8ad4…1f6b84
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de18d ago0xb0244a…b9363e
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de18d ago0x031654…4abb4a
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d19d ago0x849f7c…c6b16f
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a19d ago0x14e7a7…fb380a
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xd016…b67a20d ago0xf70158…d9dbd8
0x244b…dddd0x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a20d ago0xc638b9…4cffea
0x244b…dddd0x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a21d ago0xb086bd…e5666d
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de23d ago0xf21443…43b3f3
0x244b…dddd0x5c7b…35c5EthereumEthereum$21.0070%0xc10a…ae5d23d ago0x84070c…04b2d1
0x244b…dddd0x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a24d ago0xfbd9df…2be4a3
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de24d ago0x8630a1…222b7b
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d25d ago0xbed458…50c9c6
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5050%0xe459…e4de25d ago0x449d01…235a66
0x244b…dddd0x5c7b…35c5EthereumEthereum$21.0070%0xc10a…ae5d27d ago0x0627b0…d9dcc1
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xe459…e4de27d ago0x461230…d3439a
0x244b…dddd0x5c7b…35c5EthereumEthereum$10.5070%0xc10a…ae5d27d ago0xfb3781…b3c474

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

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

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: 0x244b…dddd

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