AgentReport

0xea78…ac6f

0xea78d9586a5323c2a16ab8aa252042169d10ac6fExplorer
$0.00
Paid out
$0.00
Received
1
Settlements
1
Distinct counterparties
Over the whole indexed history

Paid $0.00 of the $261.62M Roundhouse has indexed across 717,750 wallets.

Chains (from the recent scan): Base (1)

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.0011

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.

  • 0xae15…9d74 · last paid 75d ago
    $0.00
    1 call

    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…

Activity

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xae15…9d74$0.00$0.00175d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

all observed volume is with one counterparty, in all 1 observed settlement.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xea78…ac6f0xae15…9d74Base$0.00100%payAI75d ago0xc8de10…70a51c

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

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

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: 0xea78…ac6f

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