AgentReport

0x73d7…7289

0x73d790ec37eeefd5dfd50e9e0d6def143c477289Explorer
Paid out
$0.25
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
3
Last 7d vs prior 7d
3
Distinct counterparties
Over the whole indexed history

Paid $0.25 of the $3232.11M Roundhouse has indexed across 1,453,555 wallets — less than 0.0001% of it.

Whole-history totals from the index rollup, which can be up to 30 minutes behind.

Chains (from the recent scan): Base (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
Not in any catalogue80%$0.2011
Web & Content20%$0.0522

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; for 3 of 3 the amount paid narrows the list to the ones listed at that price.

One merchant publishes more endpoints than a single catalogue read returns; its list is partial.

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
0xabf4…a9d0$0.20$0.00143d agoGraph
0xcd67…3a39$0.04$0.00121d agoGraph
0xc751…86a1$0.01$0.00149d 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 3 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x73d7…72890xcd67…3a39BaseBase$0.04100%coinbase21d ago0x0514ba…0adde3
0x73d7…72890xabf4…a9d0BaseBase$0.20100%coinbase43d ago0x348cfb…60f4e1
0x73d7…72890xc751…86a1BaseBase$0.01100%coinbase49d ago0x3af5a9…dd1df2

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

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

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: 0x73d7…7289

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