AgentReport

0x67cc…b010

0x67cc95db8e8c94327d5828a03eced10001c6b010Explorer
Paid out
$0.72
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
715
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.72 of the $3105.10M Roundhouse has indexed across 1,405,443 wallets — less than 0.0001% of it.

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

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

$0.72 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 39d ago
    $0.45
    446 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 82d ago
    $0.27
    269 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.45$0.0044639d agoGraph
0x9c95…e299$0.27$0.0026982d agoGraph

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

Data quality

62% of observed volume is with a single counterparty, in all 715 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x120c33…8f153f
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x33a44e…c67d4d
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0xbb27d2…706e53
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x6eaf00…9cd763
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x41b80d…4b7903
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x47a698…ea3328
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x1875ca…5c2a7e
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x6bf69d…aa8690
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x3af403…a355c2
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0xd685d4…acb565
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x6bdb7e…805709
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0xbefee8…0617a9
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0xb46818…9132ea
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x73b58c…bb55d0
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x0893ce…62c51b
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x481060…74b1a4
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x72f3c4…abf15f
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x21a796…260a7c
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x658c9c…e17bf2
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x9e7d8f…e9e8f9
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x436736…2d0e59
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x2251e4…f640ef
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0xf3e907…37608f
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0xabf4cf…c7edc3
0x67cc…b0100xfe80…47eeBaseBase$0.001100%fluxa64d ago0x186613…66a23e

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

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

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: 0x67cc…b010

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