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,689 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%fluxa71d ago0x6725ce…097183
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0xbf99ba…cad561
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x20ffaf…fd2ccb
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x5ff772…4add86
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x1b9bf3…554d5a
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x367e2c…63ea79
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x9773f3…e6b72c
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0xda3a92…68d2e1
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x9e6674…995122
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x87bcd9…0eaa7e
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x1941d6…0fb1dd
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x595b9a…71efde
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x8afb8d…424680
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x18aba2…4b20ca
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0xda2ccd…173f1b
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x53d14f…24e2b3
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa71d ago0x9dc696…dd695e
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa72d ago0x3d2f0a…a9fc86
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa72d ago0x0ef2c7…f60726
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa72d ago0x13986a…b71c2c
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa72d ago0xb66fe7…040bc2
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa72d ago0x18ee84…cb66b4
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa72d ago0x540486…be67b0
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa72d ago0xc22f3f…63b905
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa73d ago0x738f0f…aba903

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.