AgentReport

0x6147…6683

0x61472075cbfa6281687fa90f18da76be746d6683Explorer
Paid out
$0.77
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
768
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.77 of the $3167.94M Roundhouse has indexed across 1,430,642 wallets — less than 0.0001% of it.

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

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

$0.77 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 58d ago
    $0.63
    632 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 79d ago
    $0.14
    136 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.63$0.0063258d agoGraph
0x9c95…e299$0.14$0.0013679d agoGraph

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

Data quality

82% of observed volume is with a single counterparty, in all 768 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0x951f24…ebe89a
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0x1413a5…f8caad
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0x63c966…a97b40
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0x5cbf67…826eb9
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xbb5339…8b99ff
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0x168fcf…3f8029
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0x40f846…975576
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xe649aa…6e5b5a
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xcb808c…e8313c
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0x8fe450…709d73
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xfbea61…949431
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0x78fca5…ac6649
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xcb197f…e22717
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xfb468e…b49e54
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xa1784f…8d036d
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0x48b0c4…530429
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xb1276c…0d1ef7
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xcb0d60…6c9ce9
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0x859592…ece65f
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xfb7cfa…dd3430
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xa3d1b0…66e8e9
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xdb7fb6…5c09db
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0x9c7f42…5b1ecf
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xdf9b81…2d6058
0x6147…66830xfe80…47eeBaseBase$0.001100%fluxa65d ago0xb0efc8…86b983

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

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

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: 0x6147…6683

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