AgentReport

0x59d8…ea36

0x59d85672dc0e191ec3f40c9b6e16babc3495ea36Explorer
Paid out
$34.17
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21743
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $34.17 of the $260.92M Roundhouse has indexed across 716,778 wallets — less than 0.0001% of it.

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

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%$3.791,0002

Every merchant paid publishes at least one catalogued endpoint.

Services it paid

A settlement carries the payee and the amount, never the URL. These are the endpoints each payee publishes; for 2 of 2 the amount paid narrows the list to the ones listed at that price.

Folded from this wallet's 1,000 most recent settlements of 21,743 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

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
0x0495…eed9$2.29$0.00850225d agoGraph
0x8324…fd0e$1.50$0.00150238d agoGraph

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

Data quality

60% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x354a39…dcddcd
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x075372…c83ba1
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x947942…0445af
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x8a98db…eb64b2
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0xf5dce1…d2e4ef
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0xf2fd3a…4bfce6
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0xbc49bf…6daf25
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0xb9f2a4…a80d00
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x2df0f2…043d4f
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x1709c3…f41fff
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0xf4f49f…0f6a8c
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0xc8b0a6…f38abc
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0xd6e3b3…6128bc
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x490c62…bf8ad1
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0xcb761b…2933be
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x117db5…59c43a
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x995031…12fe55
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x710440…b72781
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x3f4211…938cb6
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x3f4211…938cb6
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x3ebad9…79f546
0x59d8…ea360x0495…eed9Base$0.10100%payAI225d ago0x83db95…8ed455
0x59d8…ea360x0495…eed9Base$0.01100%payAI225d ago0x687b3b…1801cc
0x59d8…ea360x0495…eed9Base$0.0001100%payAI238d ago0xb4559d…1c1b15
0x59d8…ea360x0495…eed9Base$0.0001100%payAI238d ago0xc30de7…30cc1a

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

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

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: 0x59d8…ea36

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