AgentReport

0x9daa…b87b

0x9daa1590c48fcea43d4c89c6c8e6df6e5e97b87bExplorer
Paid out
$1,460.31
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
7
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $1,460.31 of the $3066.54M Roundhouse has indexed across 1,400,255 wallets — less than 0.0001% of it.

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

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%$1,460.3172

$1,460.31 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.

  • 0x7096…86ba · last paid 157d ago
    $982.36
    2 calls

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

  • 0x43be…b589 · last paid 377d ago
    $477.95
    5 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
0x7096…86ba$982.36$0.002157d agoGraph
0x43be…b589$477.95$0.005377d agoGraph

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

Data quality

67% of observed volume is with a single counterparty, in all 7 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x9daa…b87b0x7096…86baEthereumEthereum$791.1870%0xa45d…f27a157d ago0xf90da7…ada94e
0x9daa…b87b0x7096…86baEthereumEthereum$191.1870%0xa45d…f27a259d ago0x0a5742…2aa340
0x9daa…b87b0x43be…b589EthereumEthereum$95.5970%0xa45d…f27a377d ago0x2b1cc9…549fbc
0x9daa…b87b0x43be…b589EthereumEthereum$95.5970%0xa45d…f27a385d ago0xce19d7…916014
0x9daa…b87b0x43be…b589EthereumEthereum$95.5970%0xa45d…f27a413d ago0x9cb17b…26380b
0x9daa…b87b0x43be…b589EthereumEthereum$88.7770%0xa45d…f27a462d ago0x499653…1a2609
0x9daa…b87b0x43be…b589EthereumEthereum$102.4170%0xa45d…f27a466d ago0x106619…d2030b

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

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

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: 0x9daa…b87b

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