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,384 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.9035943m 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.80488h 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
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x391a7e…994aca
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xdfb107…160228
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x6d789a…dc0777
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xb98fa7…b4ad2b
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x090790…5c39e4
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xa794e2…4283bf
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xd6a400…d49a0d
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xb211b3…9ddf29
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x1999ca…ec0474
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xd80bc6…540d57
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI1d ago0x7039ae…bcccaa
0xb90c…03a30xdb5c…10fdBaseBase$0.10100%payAI1d ago0x9f23e4…1ea955
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x7e0569…27e0e3
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x4f0090…c2f508
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xc45f41…41572b
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x9020bd…a8839e
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x9eb799…7e28ec
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x873873…524b06
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xb0ec73…26bb2e
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xa12d13…74376f
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xb99041…5e7ae0
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xf3a24c…6b1404
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI1d ago0xf99c84…6c717b
0xb90c…03a30xdb5c…10fdBaseBase$0.10100%payAI1d ago0x6e8a55…fe34d7
0xdfe7…53110xdb5c…10fdBaseBase$0.10100%payAI1d ago0xabe3b4…6c1fc6

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.