AgentReport

0xfdcb…d06c

0xfdcbd0ad57dba8cdeaf9801c80a9f06bcdfcd06cExplorer
Paid out
$3,340.58
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
6
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $3,340.58 of the $3243.74M Roundhouse has indexed across 1,458,624 wallets — 0.0001% of it.

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

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%$3,340.5861

$3,340.58 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.

  • 0x7dbb…59e0 · last paid 10m ago
    $3,340.58
    6 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
0x7dbb…59e0$3,340.58$0.00610m 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 6 observed settlements.

Organic volume $3,340.58 of $3,340.58 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xfdcb…d06c0x7dbb…59e0EthereumEthereum$790.0070%0x323a…a4f210m ago0xad4571…7a4daf
0xfdcb…d06c0x7dbb…59e0EthereumEthereum$590.0070%0x323a…a4f235d ago0x82e4fd…288471
0xfdcb…d06c0x7dbb…59e0EthereumEthereum$640.0070%0x323a…a4f244d ago0xb65519…8529c5
0xfdcb…d06c0x7dbb…59e0EthereumEthereum$340.0070%0x323a…a4f254d ago0xefbca6…a6b376
0xfdcb…d06c0x7dbb…59e0EthereumEthereum$490.5870%0x323a…a4f264d ago0x0bd2aa…668592
0xfdcb…d06c0x7dbb…59e0EthereumEthereum$490.0070%0x323a…a4f272d ago0x1c72a7…80c48c

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

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

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: 0xfdcb…d06c

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