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%fluxa37d ago0x15e23a…a6badf
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0xeeee47…2e9833
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0xe7dba5…5663f6
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x441ef9…60fcbd
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x126281…4dbdaf
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0xc2e173…1babb9
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x754766…b5518b
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x3754fc…645889
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0xf3fae3…080b49
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x1cd16d…942617
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x482fd8…d2f8b0
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0xdc4c4b…10c8e4
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x9d6d02…fd2a9f
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x27fce5…f1aaaf
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x0790c9…9a7b81
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x10015a…01937b
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0xcdebb3…06e20a
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0xbe415d…0f79d3
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0xd49194…a282d9
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x7a84cf…0f0141
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x1004fe…6dfcab
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x89769b…601160
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x3cdc78…700b4b
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0xdde912…1c6490
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa37d ago0x959845…2ba277

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.