AgentReport

0x404d…7f96

0x404d51c771a03e3a9d727f2df353bda33e587f96Explorer
Paid out
$8,307.39
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
3
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $8,307.39 of the $3063.55M Roundhouse has indexed across 1,399,142 wallets — 0.0003% of it.

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

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
Onchain Data100%$8,307.3931

Every merchant paid publishes at least one catalogued endpoint.

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.

  • 0x0000…0000api.cleave.fiGas price?Endpoint up
    0x0000…0000 · last paid 50d ago
    $8,307.39
    3 calls
    ▸1 catalogued endpoints, none priced at an amount this agent paid
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
0x0000…0000$8,307.39$0.00350d 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 3 observed settlements.

Organic volume $8,307.39 of $8,307.39 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x404d…7f960x0000…0000EthereumEthereum$1,406.7070%0x5496…952750d ago0xa9bbc5…5719d2
0x404d…7f960x0000…0000EthereumEthereum$764.0470%0x5496…952761d ago0x9cf59f…fb67d8
0x404d…7f960x0000…0000EthereumEthereum$6,136.6670%0x39d6…376591d ago0xb793bf…b4ce75

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

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

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: 0x404d…7f96

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