AgentReport

0x4959…3261

0x4959ec4f01a8041aad4c4d2f0f9f31eb8d543261Explorer
Paid out
$53.00
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
53
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $53.00 of the $3067.00M Roundhouse has indexed across 1,401,091 wallets — less than 0.0001% of it.

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

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%$53.00532

$53.00 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.

  • 0x2383…fbf1 · last paid 366d ago
    $46.00
    46 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x0fe8…9393 · last paid 364d ago
    $7.00
    7 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
0x2383…fbf1$46.00$0.0046366d agoGraph
0x0fe8…9393$7.00$0.007364d agoGraph

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

Data quality

87% of observed volume is with a single counterparty, in all 53 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x4959…32610x2383…fbf1BaseBase$1.00100%coinbase366d ago0x8316e1…d01189
0x4959…32610x2383…fbf1BaseBase$1.00100%coinbase366d ago0x3ed49f…f84890
0x4959…32610x2383…fbf1BaseBase$1.00100%coinbase366d ago0xfa87d9…2db723

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

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

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: 0x4959…3261

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