AgentReport

0x4964…1427

0x4964d2b67ee0aa435f50419049d213df51e11427Explorer
Paid out
$0.97
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
967
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.97 of the $3066.54M Roundhouse has indexed across 1,400,689 wallets — less than 0.0001% of it.

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

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

$0.97 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 36d ago
    $0.69
    692 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.28
    275 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.69$0.0069236d agoGraph
0x9c95…e299$0.28$0.0027577d agoGraph

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

Data quality

72% of observed volume is with a single counterparty, in all 967 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa41d ago0x6a23ff…d9c788
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa41d ago0x12dd32…4a221b
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa46d ago0xf3373f…079175
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa46d ago0xc9133a…284cc4
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa46d ago0xc865be…cd7904
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa46d ago0xb0294e…6fcaf9
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa46d ago0x7600e3…89e4c0
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa46d ago0x25c246…beceb9
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa46d ago0xd2b710…47d3e0
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa46d ago0xdb5390…e74153
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa46d ago0xedf475…fc64e9
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa46d ago0x14db8f…9613f7
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa46d ago0xb8db76…306aaa
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0xde332e…c404f1
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0x6cdc00…3577cc
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0x4f6fe8…f8e89b
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0x3d9d1c…f26158
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0xcd664b…0fae24
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0xb6fe9b…2e57ca
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0x25bad3…5c70d8
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0xbef633…2b03c1
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0x55c284…3aa635
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0x9cc553…ebe988
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0x5dc4d5…2805f9
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa47d ago0xbff1ec…fab48e

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

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

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: 0x4964…1427

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