AgentReport

0xdd3a…da9b

0xdd3aec49aecf7d2fab46429d100bc73c8d8bda9bExplorer
Paid out
$34.08
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
21719
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $34.08 of the $262.02M Roundhouse has indexed across 718,720 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.731,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,719 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.00856226d agoGraph
0x8324…fd0e$1.44$0.00144239d agoGraph

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

Data quality

61% 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
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0xfd82f9…372963
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0xc6b173…87e3f9
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x777ae4…c080e8
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x6e9462…e86669
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0xee4d3b…e26564
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x012d18…ae58e3
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x5792b6…c0e752
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x918d04…dac0d5
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x7c91b9…10e45a
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x55031c…b280fc
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x4c2301…30b0d4
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x59f9a4…91dd74
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0xf821c7…58d923
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x9e9d60…6165b8
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x719088…c28cf8
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0xae9016…6c4a2e
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x13aff9…cc5f40
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x00c2d6…847fff
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x28f675…5456b7
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0xc87d33…60edc5
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0xa4aa36…029d27
0xdd3a…da9b0x0495…eed9Base$0.10100%payAI226d ago0x32daba…5ebf1a
0xdd3a…da9b0x0495…eed9Base$0.01100%payAI226d ago0xfd9344…9e6ecf
0xdd3a…da9b0x0495…eed9Base$0.0001100%payAI239d ago0x50842f…d5e69a
0xdd3a…da9b0x0495…eed9Base$0.0001100%payAI239d ago0x3f075d…917e96

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

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

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: 0xdd3a…da9b

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