AgentReport

0x102d…f760

0x102d381336c30014737cc7e8056ecf4a6ca1f760Explorer
Paid out
$0.90
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
898
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.90 of the $3066.54M Roundhouse has indexed across 1,400,255 wallets — less than 0.0001% of it.

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

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

$0.90 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 66d ago
    $0.53
    531 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 77d ago
    $0.37
    367 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.53$0.0053166d agoGraph
0x9c95…e299$0.37$0.0036777d agoGraph

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

Data quality

59% of observed volume is with a single counterparty, in all 898 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa67d ago0x1d9d28…7037fb
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa67d ago0x4c490c…8e74fd
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa67d ago0xe70dff…fbf74f
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa67d ago0x001c0f…d052af
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa67d ago0x7f50f9…cd9552
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa67d ago0x6ba698…2c33ae
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa67d ago0x1e1bdc…0a64e0
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0xaa630e…24e427
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0xeb068b…68cd7f
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0x71c6d7…8e3192
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0x5f4292…0c080f
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0xcc4e42…f920e8
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0x5159bb…9f3928
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0x4eec17…c61f83
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0x358cc1…755166
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0xe93820…048e28
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0xc20027…c7a391
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0x570593…e6b77a
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0xc27411…13553f
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0x95e456…313024
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0xab5238…0ece89
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0x1b5275…46cf73
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0x33cd4e…a4ddcb
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0x90e410…5fb3b3
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa68d ago0xc005fe…b4eb3a

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

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

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: 0x102d…f760

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