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 $3067.43M Roundhouse has indexed across 1,401,742 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%fluxa65d ago0x40d1d3…03fe93
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa65d ago0x0de8c8…43899c
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa65d ago0x0b1f0b…867a84
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa65d ago0xc17602…b32152
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa65d ago0x540625…7c4852
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa65d ago0xc5be88…b21825
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa65d ago0x319e8c…d1caa8
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa65d ago0x083aa9…4551cc
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xda850d…ea8b6f
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x2e5e37…eb000b
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x14cbf3…d37668
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xbaa7d0…1031c5
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xc3c555…bcd558
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x636b6a…b44f86
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x1de170…b608d4
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xf28a7d…a28ac2
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x0208ee…5caca9
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x52975d…c4323c
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xc114c5…e48044
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xcf0cd2…350e3c
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x362c8b…eca9ee
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x5a58f1…45d640
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x4af128…90e1e9
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xa96425…7b91e5
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xe05470…ab418e

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.