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,400,982 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%daydreams323d ago0x2b677f…9c670d
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams323d ago0x86d344…674a3b
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams323d ago0x731682…3d6a78
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams323d ago0xbe3048…fee976
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams324d ago0x99c714…e386dd
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams324d ago0x6a5ff4…88a485
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams324d ago0xa41315…356f25
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams324d ago0x0dbf98…418aee
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams324d ago0x37b64c…807a9d
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams324d ago0xdd03bb…870e7d
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams324d ago0x67542c…1dd4b3
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams324d ago0x3f805c…3eab08
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams324d ago0x53ae54…60b8de
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams324d ago0xd0fdc7…8dd452
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams325d ago0x8fad26…0c3c60
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams325d ago0x737cad…640d4f
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams325d ago0xadd93d…700c2c
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams325d ago0x9ea369…c4bb9e
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams325d ago0x1b04ba…3c7009
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams325d ago0x4a8cf1…401e76
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams325d ago0xdc2857…366b79
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams325d ago0x441551…fb0958
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams325d ago0x621c6d…fc766f
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams325d ago0x40f3ec…8fe1d3
0x100c…68e20x6482…b779BaseBase$0.0001100%daydreams325d ago0xf6a43a…040538

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.