AgentReport

0x95b5…d0a4

0x95b541e18491892571841ac818917c391b38d0a4Explorer
Paid out
$2.73
Last 7d vs prior 7d
Received
$2.73
Last 7d vs prior 7d
Settlements
22
Last 7d vs prior 7d
4
Distinct counterparties
Over the whole indexed history

Paid $2.73 of the $3217.99M Roundhouse has indexed across 1,446,219 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 (22)

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

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

  • 0x72ab…a2db · last paid 22d ago
    $2.73
    10 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
0x72ab…a2db$2.73$0.001022d agoGraph
0xe88d…9221$0.00$1.84822d agoGraph
0xab79…787d$0.00$0.54222d agoGraph
0xd1ae…8133$0.00$0.352128d 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 22 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x95b5…d0a40x72ab…a2dbBaseBase$0.54100%fluxa22d ago0x9c9dcf…c291f7
0xab79…787d0x95b5…d0a4BaseBase$0.34100%fluxa22d ago0x91ee6a…725ae2
0xe88d…92210x95b5…d0a4BaseBase$0.20100%fluxa22d ago0xaab3ec…ce619b
0x95b5…d0a40x72ab…a2dbBaseBase$0.10100%fluxa28d ago0x1b16f6…077fef
0xe88d…92210x95b5…d0a4BaseBase$0.10100%fluxa28d ago0xc92d4e…d6b03b
0x95b5…d0a40x72ab…a2dbBaseBase$0.30100%fluxa38d ago0xe3e704…d36bee
0xab79…787d0x95b5…d0a4BaseBase$0.20100%fluxa38d ago0x5e6c20…5661bc
0xe88d…92210x95b5…d0a4BaseBase$0.10100%fluxa38d ago0x64cd74…7682d4
0x95b5…d0a40x72ab…a2dbBaseBase$0.10100%fluxa57d ago0x446e17…a27da4
0xe88d…92210x95b5…d0a4BaseBase$0.10100%fluxa58d ago0xd801c7…a4c09d
0x95b5…d0a40x72ab…a2dbBaseBase$0.08100%fluxa71d ago0x5f3f51…2eff92
0xe88d…92210x95b5…d0a4BaseBase$0.08100%fluxa71d ago0xb7ed64…a47356
0x95b5…d0a40x72ab…a2dbBaseBase$0.86100%fluxa89d ago0x70610e…14be1e
0xe88d…92210x95b5…d0a4BaseBase$0.86100%fluxa90d ago0x7d0e01…bbdb7e
0x95b5…d0a40x72ab…a2dbBaseBase$0.30100%fluxa98d ago0xee67d0…9a5e38
0xe88d…92210x95b5…d0a4BaseBase$0.30100%fluxa99d ago0x7aa9ea…045ee0
0x95b5…d0a40x72ab…a2dbBaseBase$0.10100%fluxa101d ago0xc27b70…4f5c97
0xe88d…92210x95b5…d0a4BaseBase$0.10100%fluxa101d ago0x8f5626…e8e61a
0x95b5…d0a40x72ab…a2dbBaseBase$0.10100%fluxa127d ago0x83cca5…04055e
0xd1ae…81330x95b5…d0a4BaseBase$0.10100%fluxa128d ago0xee64b6…7bffb1
0x95b5…d0a40x72ab…a2dbBaseBase$0.25100%fluxa156d ago0x95175e…e7f1d3
0xd1ae…81330x95b5…d0a4BaseBase$0.25100%fluxa156d ago0xa13b38…ce0128

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

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

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: 0x95b5…d0a4

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