AgentReport

0x2692…145c

0x26920508982821137272dde48aa4eaa6e8d4145cExplorer
Paid out
$2,662.97↑ 58%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
58→ 0%
Last 7d vs prior 7d
5
Distinct counterparties
Over the whole indexed history

Paid $2,662.97 of the $3060.21M Roundhouse has indexed across 1,397,618 wallets — less than 0.0001% of it.

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

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%$2,662.97585

$2,662.97 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.

  • 0xcf3d…b9fc · last paid 81d ago
    $1,454.77
    30 calls

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

  • 0x42ec…7160 · last paid 418d ago
    $633.90
    10 calls

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

  • 0xc148…3515 · last paid 1d ago
    $325.98
    11 calls

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

  • 0xbce3…2e54 · last paid 82d ago
    $178.53
    5 calls

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

  • 0x78f6…c215 · last paid 77d ago
    $69.78
    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
0xcf3d…b9fc$1,454.77$0.003081d agoGraph
0x42ec…7160$633.90$0.0010418d agoGraph
0xc148…3515$325.98$0.00111d agoGraph
0xbce3…2e54$178.53$0.00582d agoGraph
0x78f6…c215$69.78$0.00277d agoGraph

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

Data quality

55% of observed volume is with a single counterparty, in all 58 observed settlements.

Recent activity

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

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

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: 0x2692…145c

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