AgentReport

0x100c…68e2

0x100cecc87508c1526d4116b8ef1d3638ff5b68e2Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
261
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 (261)

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

$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
    261 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.00261276d 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 261 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams337d ago0x2968b3…5af1ed
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams337d ago0x7f98ea…c6f75b
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams337d ago0xfb4422…711dbb
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams338d ago0x6e9fde…92a185
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams338d ago0x3a79d4…c50f43
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams338d ago0xd215f1…53e211
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams338d ago0xbc7bea…fab564
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams338d ago0xe5a0ca…4f9ae7
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams339d ago0x85f760…7fab11
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams339d ago0x31cb01…b22bd4
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams339d ago0xa06c97…af5594
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams339d ago0xdbfc5a…2ac0b0
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams339d ago0x51bf35…eed14d
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams340d ago0x6e823a…008e26
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams340d ago0x88f00e…8f51e0
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams340d ago0x28e9cd…08b0ae
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams340d ago0xa39b66…4727a7
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams340d ago0xc1b9d7…ff4d02
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams340d ago0x3dc4d6…529109
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams340d ago0x9bfbdd…869402
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams340d ago0x97347b…989926
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams340d ago0xe1e52e…7bd856
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams340d ago0x9bc721…ae6a9e
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams340d ago0x5c9192…941876
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams341d ago0x55dcdf…9da0e0

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

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

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: 0x100c…68e2

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