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.9035933m 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
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI33m ago0xbc0753…7bc66b
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI2h ago0x2c2207…8cb9fe
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI5h ago0x1d0b62…758b47
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI8h ago0x85b37f…9477d8
0x4dbe…6beb0xdb5c…10fdBaseBase$0.10100%payAI8h ago0x9ca41d…745129
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI9h ago0xc80a42…0d565c
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI11h ago0x1584e8…c2d6a9
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI15h ago0x51397c…034f6b
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI18h ago0xcd9605…ae574d
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI21h ago0xbc0ecc…772dec
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x491077…ba06b5
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xcb4444…ccae37
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x4a836f…9ef869
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xe221e3…bba543
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x094719…f69130
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x710043…4edfed
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0x5e245c…d397d5
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xf7c662…f1af6a
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xc82baf…48890f
0x9fdd…d95f0xdb5c…10fdBaseBase$0.10100%payAI1d ago0xb58674…bab730
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI1d ago0x0587fa…0dca1d
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI1d ago0x3097e9…9fa12b
0xb90c…03a30xdb5c…10fdBaseBase$0.10100%payAI1d ago0xba7eed…0942ef
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI1d ago0xfc81b3…bacb66
0x3e19…e2400xdb5c…10fdBaseBase$0.10100%payAI1d ago0xef7fbd…883314

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.