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.00M Roundhouse has indexed across 1,401,091 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%fluxa66d ago0x1850ad…3c4418
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xbd3ce4…058604
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x131ee1…9b9179
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x492a23…c2a752
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xd30b6b…0d53bd
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xd63a92…e5a52f
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x26b9b0…ae5573
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xda5b83…913102
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x1f12cb…c8d395
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x0093ef…e33092
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x882089…f3f270
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x5813a3…dfd2c6
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xeaa198…dbcaeb
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x91f3c2…521a7e
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x2b264a…b80775
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0xe26b19…10ea4c
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x0c104c…c5b621
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x0cffcf…255d3e
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x713902…137936
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x486a2e…2a4504
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa66d ago0x7525d9…72017b
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa67d ago0xf5173a…12b158
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa67d ago0xf07923…9141e1
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa67d ago0x252eb2…6d5309
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa67d ago0x9e0eb5…f276de

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.