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,575 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%fluxa74d ago0x492dcc…473ed6
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa74d ago0xe4930a…833a66
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa74d ago0xcbbd4d…853a7c
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa74d ago0x90e70b…be0132
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa74d ago0x5c8b5d…066b0d
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x399bd4…7bc709
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0xf29351…3bbe35
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x884bf0…0f9e33
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x3849c0…2030c8
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0xc91811…e8967e
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0xbb3302…71b452
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x8b5005…e220fa
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0xb7c9c5…d55dfa
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x47b576…b03d0d
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0xbabc40…54871a
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x3ac82a…5b09c0
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x17f47a…b1288d
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x454795…bf9aa1
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x0ba818…4d71b9
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x2c5908…88d1cb
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0xa448a4…8be518
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0xd8c24b…a38e7a
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x8118dc…f34967
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x471e3c…9af7b6
0x102d…f7600xfe80…47eeBaseBase$0.001100%fluxa75d ago0x464639…8d1487

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.