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.25M Roundhouse has indexed across 1,401,192 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%fluxa69d ago0x5f862f…733df8
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x05898a…588b79
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x49764e…cc8d4b
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x990c90…674d01
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0xc9ead5…f7cdc8
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x03e7f6…f6348e
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0xb99ddb…e2012e
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x15086d…cd4035
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0xf89b9f…dfce25
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x678699…3b6ed6
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0xc31119…c74f91
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x56014b…281bfd
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x7c1244…5324ba
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0xaab346…45e632
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x1ba343…5ce80b
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x16b80a…2f6c1e
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0xe2ca10…770710
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0xe3eba5…476c04
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x56b7fd…51b93a
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0xd10911…58613f
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x901670…8295b4
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0xa8e3bb…55895b
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x01057a…bd34d9
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0xd906f2…6f00a8
0x4964…14270xfe80…47eeBaseBase$0.001100%fluxa69d ago0x59fdb4…9c9fa5

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.