AgentReport

kamildemir.eth

0xf57f0a8ab90fbe074072a9fd641806a0085407edExplorer
Kamildemir.eth
Paid out
$20.85→ 0%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
208→ 0%
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $20.85 of the $3064.22M Roundhouse has indexed across 1,399,289 wallets — less than 0.0001% of it.

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

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

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

  • 0x7d2c…bcfe · last paid 5d ago
    $20.85
    208 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
0x7d2c…bcfe$20.85$0.002085d 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 208 observed settlements.

Organic volume $20.85 of $20.85 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase77d ago0xa94cb8…30a98c
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase77d ago0xea59dd…19f5e5
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase77d ago0x55c0bc…92bc2d
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase77d ago0xcaa57a…1547e5
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase77d ago0xebd554…6fcf5a
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase77d ago0xc450d5…e78c9d
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase87d ago0xf74cdf…5cda61
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase87d ago0x835585…d2ff02
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase87d ago0xf9c767…d56480
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase87d ago0x6696d9…266bcf
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase87d ago0xf90621…6eeffa
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase87d ago0x113bc9…8194e3
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase87d ago0x9d83cc…cd8d5d
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase92d ago0xce0ea2…7f38ae
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase92d ago0x2531a8…6c0913
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase92d ago0x34c186…c06ad1
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase92d ago0xfe8b32…6a795c
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase92d ago0x79ac77…1df9d6
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase92d ago0x09892b…9eb633
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase92d ago0xba2dce…7a9056
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase95d ago0xa30450…d5a9f8
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase95d ago0x152597…98d1dd
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase95d ago0xc9822c…5860a8
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase95d ago0x42fb15…7765bd
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase95d ago0x2534ef…d8c9c2

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 kamildemir.eth has actually paid for over the free read API. No key, no account.

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

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: kamildemir.eth

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