AgentReport

0x07b3…5e7b

0x07b3389ee107827754cec0d286cb4007379b5e7bExplorer
Paid out
$155.40
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
5
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $155.40 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

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

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%$155.4051

$155.40 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 15m ago
    $155.40
    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
0x5c7b…35c5$155.40$0.00515m 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 5 observed settlements.

Organic volume $155.40 of $155.40 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x07b3…5e7b0x5c7b…35c5EthereumEthereum$52.5070%0xd016…b67a15m ago0xaf7892…b04ef2
0x07b3…5e7b0x5c7b…35c5EthereumEthereum$21.0070%0xd016…b67a15d ago0x6b7d19…31712a
0x07b3…5e7b0x5c7b…35c5EthereumEthereum$21.0070%0xe459…e4de41d ago0x713b24…469cbb
0x07b3…5e7b0x5c7b…35c5EthereumEthereum$47.2550%0xc10a…ae5d78d ago0x643b17…ccb5c5
0x07b3…5e7b0x5c7b…35c5EthereumEthereum$13.6570%0xd016…b67a116d ago0x8a2df8…1962ea

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

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

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: 0x07b3…5e7b

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