AgentReport

0xc589…4bde

0xc58947dd6f5cfb6279bb2da4fc719e6034824bdeExplorer
Paid out
$0.001321
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
3
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.001321 of the $261.16M Roundhouse has indexed across 717,066 wallets — less than 0.0001% of it.

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

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.00132132

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

  • 0x6713…190c · last paid 306d ago
    $0.00092
    2 calls

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

  • 0x4944…4bf3 · last paid 317d ago
    $0.000401
    1 call

    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

MarAprMayJunJulAugSep
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x6713…190c$0.00092$0.002306d agoGraph
0x4944…4bf3$0.000401$0.001317d agoGraph

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

Data quality

70% of observed volume is with a single counterparty, in all 3 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc589…4bde0x6713…190cBase$0.000293100%questflow306d ago0x4687a6…acf3af
0xc589…4bde0x6713…190cBase$0.000627100%questflow317d ago0xaf8122…64b258
0xc589…4bde0x4944…4bf3Base$0.000401100%questflow317d ago0x7c13bd…823b67

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

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

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: 0xc589…4bde

curl -s 'https://api.roundhouseai.io/v0/agents/0xc58947dd6f5cfb6279bb2da4fc719e6034824bde'
curl -s 'https://api.roundhouseai.io/v0/entities/0xc58947dd6f5cfb6279bb2da4fc719e6034824bde/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.