AgentReport

0x227d…f672

0x227d2f1f7a018dc24767a6ea512937a202ddf672Explorer
Paid out
$5,001.74↑ 300%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
8↑ 300%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $5,001.74 of the $3053.48M Roundhouse has indexed across 1,395,044 wallets — 0.0002% of it.

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

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%$5,001.7482

$5,001.74 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.

  • 0x5c7b…35c5 · last paid 7h ago
    $4,001.74
    6 calls

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

  • 0xfd78…d002 · last paid 38d ago
    $1,000.00
    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
0x5c7b…35c5$4,001.74$0.0067h agoGraph
0xfd78…d002$1,000.00$0.00238d agoGraph

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

Data quality

80% of observed volume is with a single counterparty, in all 8 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x227d…f6720x5c7b…35c5EthereumEthereum$500.0070%0x8b56…9aff7h ago0x71e414…316ecc
0x227d…f6720x5c7b…35c5EthereumEthereum$500.0070%0x07ae…0e671d ago0xde6c8f…f0348a
0x227d…f6720x5c7b…35c5EthereumEthereum$500.0070%0x8b56…9aff5d ago0x13327e…22794e
0x227d…f6720x5c7b…35c5EthereumEthereum$500.0070%0xc99d…a8f46d ago0xca71d4…d2dbda
0x227d…f6720x5c7b…35c5EthereumEthereum$500.0070%0x8b56…9aff11d ago0xa54e56…b2291b
0x227d…f6720x5c7b…35c5EthereumEthereum$1,501.7470%0xe748…9a1117d ago0xcad657…06adfc
0x227d…f6720xfd78…d002EthereumEthereum$500.0070%0x3943…d1bd38d ago0xfe12d7…2049f9
0x227d…f6720xfd78…d002EthereumEthereum$500.0070%0x3943…d1bd39d ago0x0a7dc7…943eb6

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

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

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: 0x227d…f672

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