AgentReport

0xdb5c…10fd

0xdb5c2df47e4a6df74edeb6de3159ae38b8cc10fdExplorer
Paid out
$30.00
Last 7d vs prior 7d
Received
$697.00↓ 71%
Last 7d vs prior 7d
Settlements
5575↑ 105%
Last 7d vs prior 7d
112
Distinct counterparties
Over the whole indexed history

Paid $30.00 of the $3059.84M Roundhouse has indexed across 1,397,496 wallets — less than 0.0001% of it.

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

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

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; no listed price matches an amount this agent paid, so nothing narrows them.

  • 0xa946…2101merchant.payai.networkEndpoint up
    0xa946…2101 · last paid 46d ago
    $30.00
    1 call
    ▸1 catalogued endpoints, none priced at an amount this agent paid

Folded from this wallet's 1,001 most recent settlements of 5,575 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

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x4922…4d57$0.00$88.0026d agoGraph
0x3e19…e240$0.00$35.903591h agoGraph
0xa946…2101$30.00$0.00146d agoGraph
0xe5e6…1e4a$0.00$16.801682d agoGraph
0x1328…a5d5$0.00$13.901396d agoGraph
0xab21…d070$0.00$13.3013328d agoGraph
0x4dbe…6beb$0.00$4.80489h agoGraph
0x9fdd…d95f$0.00$3.50351d agoGraph

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

Data quality

Not enough of this address's history was examined to assess it: self_dealing and counterparty_concentration and single_counterparty were computed over the 1001 most recent settlements scanned (its history is longer than the 2000-row scan cap), so nothing found there rules anything out. This is an incomplete check, not a clean record.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb90c…03a30xdb5c…10fdBaseBase$0.10100%payAI2d ago0x85f2da…7175cc
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x58a7db…af7bcd
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xdb2628…a8a9ea
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xb8a22f…b6e9ed
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x4e5cb7…4e014d
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x8e79de…706f0c
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x0b7fa5…206108
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x14c0ef…bd589e
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x0cf446…971ccb
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x96fe20…1f1fc4
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x802b19…b19ea1
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xf33728…a50925
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xdb0f22…41e9de
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xb7fea5…9f78ee
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x8d3d4b…7eb277
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x035a6d…5d38ab
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xbbe6d3…5a78e2
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x79c4e1…7dca84
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xb2fd5e…12da58
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x9a3cd5…61cad6
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xec1ead…6b66d3
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xc3696c…09bb42
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x8ea9ff…9274a4
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x0e7bf8…b59e38
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x712720…1a4267

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

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

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: 0xdb5c…10fd

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