AgentReport

0xdb5c…10fd

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

Paid $30.00 of the $3060.21M Roundhouse has indexed across 1,397,618 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,576 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$36.0036015s agoGraph
0xa946…2101$30.00$0.00146d agoGraph
0xe5e6…1e4a$0.00$16.801682d agoGraph
0x1328…a5d5$0.00$13.801386d agoGraph
0xab21…d070$0.00$13.3013328d agoGraph
0x4dbe…6beb$0.00$4.804810h 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
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xe751ef…e1f99d
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xb46008…b46d41
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x76ddeb…e00216
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x354737…96742b
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xe2fe72…98c2a2
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x858fb9…fba129
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x47dc3f…bb7117
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xf039cd…514615
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x3eb20f…d3f065
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x5b9367…cfa5f5
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x7ce91f…c81430
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x58d03d…0107bd
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x318f55…55b784
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x5ca186…749fc1
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xa76415…d5bf36
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xd92d19…7af392
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x670345…c78f4a
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x40a339…71cf44
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xf9bfb2…824b18
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x96bdec…633708
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x6cd4b0…011d57
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xe89330…73ed23
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x49b694…3b8a49
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0xec0694…c135e1
0xe5e6…1e4a0xdb5c…10fdBaseBase$0.10100%payAI2d ago0x4ce0b4…4bda92

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.