AgentReport

0x87fe…f135

0x87fea7d2be01337f3e1a67f00e357742bc72f135Explorer
Paid out
$0.81
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
807
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.81 of the $3167.94M Roundhouse has indexed across 1,430,642 wallets — less than 0.0001% of it.

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

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

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

  • 0xfe80…47ee · last paid 56d ago
    $0.67
    668 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9c95…e299 · last paid 79d ago
    $0.14
    139 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
0xfe80…47ee$0.67$0.0066856d agoGraph
0x9c95…e299$0.14$0.0013979d agoGraph

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

Data quality

83% of observed volume is with a single counterparty, in all 807 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0xcd9345…869b65
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0x8b316f…a79140
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0xee487d…acd643
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0x1e85c8…0ee955
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0x4eb70c…edafe2
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0x8e35c0…bb86fe
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0x347525…4359b0
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0x33d400…faaca7
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0x7671c6…ee6194
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0x50d8eb…4c81f5
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0xec1a54…c9c353
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0xad953e…3b10ad
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0xf38e73…7aeed2
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0xacd7ea…51e541
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa68d ago0x0894ba…8eb3fa
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa69d ago0x1083b6…74cbed
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa69d ago0xcb933f…beb2b5
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa69d ago0xedd05d…b32330
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa69d ago0x35d942…847fc3
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa69d ago0x78d218…c83c05
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa69d ago0x63e7ee…6ac00a
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa69d ago0xe8fd7a…31bf02
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa69d ago0x70b019…ad6c5f
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa69d ago0x940fef…c0b4b5
0x87fe…f1350xfe80…47eeBaseBase$0.001100%fluxa69d ago0x9f9ea8…f99783

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

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

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: 0x87fe…f135

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