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 $3063.55M Roundhouse has indexed across 1,399,142 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%coinbase5d ago0x9d24e5…34827b
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase5d ago0x7c3a4f…24349c
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase5d ago0xe9c48e…d3b4bb
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase5d ago0xbae9a5…e0e0dd
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase5d ago0x5079d5…3fd36b
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase5d ago0x9046b1…7c41fb
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase5d ago0x445b67…80e3b0
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase6d ago0x9498e3…ce6617
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase6d ago0x4e6cfe…a85099
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase6d ago0xc1128c…fc34fe
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase6d ago0x2e6dcb…06313f
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase6d ago0xe88c32…4de1dd
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase6d ago0xf96942…dbac09
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase6d ago0x077266…d1f706
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase64d ago0xa1f28f…887034
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase64d ago0xe5434d…7ceab1
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase64d ago0xaa1883…a1b819
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase64d ago0x2306ca…461dc8
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase64d ago0xa60cd0…41cf29
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase64d ago0xd83236…195db1
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase64d ago0x42b015…ba3c91
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase68d ago0x1041f9…ab876b
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase68d ago0xcc5a93…6663fe
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase68d ago0x24395b…ce1479
kamildemir.eth0x7d2c…bcfeBaseBase$0.05100%coinbase68d ago0x537c27…918902

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.