AgentReport

0x0655…ab17

0x065508c66085ba57cbe53d18749f6f6aaf31ab17Explorer
$0.01
Paid out
$0.02
Received
3
Settlements
2
Distinct counterparties
In the 3 settlements scanned

Paid $0.01 of the $3201.55M Roundhouse has indexed across 1,438,476 wallets — less than 0.0001% of it.

Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.

Chains (from the recent scan): Robinhood Chain (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.0111

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

  • 0x4e64…337a · last paid 37d ago
    $0.01
    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…

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x84f2…6149$0.00$0.02237d agoGraph
0x4e64…337a$0.01$0.00137d agoGraph

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

Data quality

67% of observed volume is with a single counterparty, in all 3 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x0655…ab170x4e64…337aRobinhood ChainRobinhood Chain$0.0170%0x81da…231937d ago0x5c3754…f3ad0f
0x84f2…61490x0655…ab17Robinhood ChainRobinhood Chain$0.0170%0x81da…231937d ago0xc0107a…220271
0x84f2…61490x0655…ab17Robinhood ChainRobinhood Chain$0.0170%0x81da…231937d ago0x8ce84e…3df050

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

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

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: 0x0655…ab17

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