AgentReport

0x258b…ab4d

0x258bd70cbff6e7b767b78a21f119dd43777bab4dExplorer
Paid out
$2.68
Last 7d vs prior 7d
Received
$2.68
Last 7d vs prior 7d
Settlements
155
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $2.68 of the $3222.19M Roundhouse has indexed across 1,448,646 wallets — less than 0.0001% of it.

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

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

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

  • 0xac65…4417 · last paid 141d ago
    $2.68
    31 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
0xac65…4417$2.68$0.0031141d agoGraph
0xb90a…9ae4$0.00$2.68124142d agoGraph

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

Data quality

50% of observed volume is with a single counterparty, in all 155 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb90a…9ae40x258b…ab4dBaseBase$0.03100%fluxa167d ago0x13e6ca…9a7d0f
0x258b…ab4d0xac65…4417BaseBase$0.02100%fluxa168d ago0x5532fc…c95f78
0xb90a…9ae40x258b…ab4dBaseBase$0.02100%fluxa168d ago0xc29ddb…c9cfa8
0x258b…ab4d0xac65…4417BaseBase$0.04100%fluxa169d ago0x3fd394…eb7087
0xb90a…9ae40x258b…ab4dBaseBase$0.04100%fluxa169d ago0x3606f4…290ac5

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

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

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: 0x258b…ab4d

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