AgentReport

0x7853…b293

0x785363a01c31ae77956b2209d3ce27661c90b293Explorer
Paid out
$1,954.05
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
18
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $1,954.05 of the $3216.06M Roundhouse has indexed across 1,444,903 wallets — less than 0.0001% of it.

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

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,954.05181

$1,954.05 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 15d ago
    $1,954.05
    18 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$1,954.05$0.001815d 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 18 observed settlements.

Organic volume $1,954.05 of $1,954.05 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7853…b2930x5c7b…35c5EthereumEthereum$204.7570%0xd016…b67a15d ago0x048ada…131279
0x7853…b2930x5c7b…35c5EthereumEthereum$189.0070%0xd016…b67a35d ago0xef8018…eee3c8
0x7853…b2930x5c7b…35c5EthereumEthereum$262.5070%0xc10a…ae5d54d ago0x388b39…eadb97
0x7853…b2930x5c7b…35c5EthereumEthereum$199.5050%0xc10a…ae5d66d ago0x9503ab…f28e88
0x7853…b2930x5c7b…35c5EthereumEthereum$99.7570%0xc10a…ae5d74d ago0x80bfc7…02224e
0x7853…b2930x5c7b…35c5EthereumEthereum$203.7070%0xd016…b67a92d ago0x38a129…2110cd
0x7853…b2930x5c7b…35c5EthereumEthereum$147.0070%0xc10a…ae5d106d ago0xa4e0c0…d6b863
0x7853…b2930x5c7b…35c5EthereumEthereum$100.8050%0xd016…b67a113d ago0x0a54be…3085e0
0x7853…b2930x5c7b…35c5EthereumEthereum$89.2570%0xd016…b67a133d ago0xd1015f…d53b06
0x7853…b2930x5c7b…35c5EthereumEthereum$84.0070%0xe459…e4de140d ago0xecbfef…bab54d
0x7853…b2930x5c7b…35c5EthereumEthereum$36.7570%0xe0df…59a1148d ago0xc65c50…3572f5
0x7853…b2930x5c7b…35c5EthereumEthereum$69.3070%0xc10a…ae5d157d ago0x9fbc75…9e368d
0x7853…b2930x5c7b…35c5EthereumEthereum$78.7570%0xe459…e4de169d ago0x6562ac…eb1357
0x7853…b2930x5c7b…35c5EthereumEthereum$42.0070%0xd016…b67a179d ago0x7064fc…8eff86
0x7853…b2930x5c7b…35c5EthereumEthereum$46.2070%0xc10a…ae5d190d ago0x62e7a1…7b49de
0x7853…b2930x5c7b…35c5EthereumEthereum$45.1570%0xd016…b67a207d ago0x469cb0…ee4507
0x7853…b2930x5c7b…35c5EthereumEthereum$24.1570%0xd016…b67a218d ago0x821168…e8a165
0x7853…b2930x5c7b…35c5EthereumEthereum$31.5070%0xe459…e4de221d ago0x6c700c…cc0f08

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

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

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: 0x7853…b293

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