AgentReport

0x75e7…ae8f

0x75e7d159662d7a18e1d5574d88c8ce2d0ba0ae8fExplorer
Paid out
$0.30
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 $0.30 of the $260.74M Roundhouse has indexed across 716,479 wallets — less than 0.0001% of it.

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 catalogue100%$0.3031

$0.30 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.

  • 0x3ddd…9ca5 · last paid 329d ago
    $0.30
    3 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

MarAprMayJunJulAugSep
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x3ddd…9ca5$0.30$0.003329d 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 $0.30 of $0.30 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x75e7…ae8f0x3ddd…9ca5Base$0.10100%coinbase329d ago0x3d1c36…7cce65
0x75e7…ae8f0x3ddd…9ca5Base$0.10100%coinbase330d ago0x740000…eaebb7
0x75e7…ae8f0x3ddd…9ca5Base$0.10100%coinbase331d ago0x2361ed…a6119b

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

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

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: 0x75e7…ae8f

curl -s 'https://api.roundhouseai.io/v0/agents/0x75e7d159662d7a18e1d5574d88c8ce2d0ba0ae8f'
curl -s 'https://api.roundhouseai.io/v0/entities/0x75e7d159662d7a18e1d5574d88c8ce2d0ba0ae8f/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.