AgentReport

0x5015…4121

0x5015b59368b4c3391f08d997cd3f0e8a01814121Explorer
Paid out
$0.21
Last 7d vs prior 7d
Received
$0.01
Last 7d vs prior 7d
Settlements
9
Last 7d vs prior 7d
5
Distinct counterparties
Over the whole indexed history

Paid $0.21 of the $260.32M Roundhouse has indexed across 716,001 wallets — less than 0.0001% of it.

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

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

$0.01 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; for 3 of 5 the amount paid narrows the list to the ones listed at that price.

  • 0xbe5c…9d30backend-production-716d3.up.railway.appEndpoint up
    0xbe5c…9d30 · last paid 5d ago
    $0.16
    3 calls
    ▸1 of 1 catalogued endpoints list a price this agent paid
  • 0x59d7…4618x402.spendthebits.comEndpoint up
    0x59d7…4618 · last paid 5d ago
    $0.03
    2 calls
    ▸1 of 1 catalogued endpoints list a price this agent paid
  • 0x82b3…f039 · last paid 5d ago
    $0.01
    1 call

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

  • 0xf52c…5678 · last paid 1d ago
    $0.003
    1 call

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

  • 402Signal402signal.comEndpoint up
    0xa260…4fa0 · last paid 5d ago
    $0.003
    1 call
    ▸1 of 1 catalogued endpoints list a price this agent paid
    • /routePrice match$0.003 listed
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
0xbe5c…9d30$0.16$0.0145d agoGraph
0x59d7…4618$0.03$0.0025d agoGraph
0x82b3…f039$0.01$0.0015d agoGraph
0xf52c…5678$0.003$0.0011d agoGraph
402Signal$0.003$0.0015d agoGraph

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

Data quality

79% of observed volume is with a single counterparty, in all 9 observed settlements.

Recent activity

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

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

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: 0x5015…4121

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