AgentReport

0x06ce…b7dc

0x06ceed51279a734f41b6d6d475ee7a0215d5b7dcExplorer
Paid out
$0.000507
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
4
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.000507 of the $3068.58M Roundhouse has indexed across 1,402,563 wallets — less than 0.0001% of it.

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

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

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

  • 0x7c8a…c27c · last paid 173d ago
    $0.000269
    2 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0xfe86…e407 · last paid 185d ago
    $0.000238
    2 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
0x7c8a…c27c$0.000269$0.002173d agoGraph
0xfe86…e407$0.000238$0.002185d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

53% of observed volume is with a single counterparty, in all 4 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x06ce…b7dc0x7c8a…c27cEthereumEthereum$0.00016170%0xda51…cf0e173d ago0xdaffac…3933bd
0x06ce…b7dc0x7c8a…c27cEthereumEthereum$0.00010870%0xa988…b115179d ago0xcaf853…b5d8dc
0x06ce…b7dc0xfe86…e407EthereumEthereum$0.00003170%0xee52…efd5185d ago0x75dd51…ea320f
0x06ce…b7dc0xfe86…e407EthereumEthereum$0.00020770%0xb853…5bce188d ago0xa82355…63f5dd

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

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

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: 0x06ce…b7dc

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