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 $3067.43M Roundhouse has indexed across 1,401,742 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%fluxa76d ago0xeaf31c…a806b3
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa76d ago0x0a7526…0b7571
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa76d ago0x28823a…ccb8c9
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa76d ago0xe2592d…c3138d
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa76d ago0x241c5e…011134
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa76d ago0x40b468…7eb787
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa76d ago0xfffa8c…38b376
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x2f219e…980d53
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x7a3a04…fff6ed
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x6758ee…ec7c23
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0xef78c6…916892
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x36405e…0255db
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x8f154a…7c6e5c
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0xef89c7…83ee19
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x1874d6…8a4f4a
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0xb79768…61b819
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x0fe6cf…57c926
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x81ec04…9d5714
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0xb48237…62070c
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x378305…45a0c5
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0xd60f44…7eabcb
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x6dc9ad…15e15b
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x31acf1…d3e16d
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x1de72c…628f8c
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa77d ago0x9515b6…74955b

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.