AgentReport

0x19ec…6a6f

0x19eca687287967aad28081411c7f07a1de6b6a6fExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
253
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

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

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

$0.03 went to wallets that publish no endpoint in any catalogue we crawl — spend we can see and cannot describe.

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.

  • 0x6482…b779 · last paid 277d ago
    $0.03
    253 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

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
0x6482…b779$0.03$0.00253277d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 253 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams349d ago0xefdab5…abbe46
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams349d ago0x3d17fb…23fc86
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams349d ago0xd899cf…5c2f6f
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams350d ago0xb3bf78…53d39a
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams350d ago0x96f422…23d4b2
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams350d ago0xc1bc65…a71e03
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams350d ago0xf608bc…0570cb
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams351d ago0xb8b7ce…31e507
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x2fa4af…6d55fc
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x96e747…225a7a
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x223174…d378c7
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x57ed13…28fc89
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams351d ago0x47a624…08ff25
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xcad31b…cd5c51
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xda5bea…a8f1bb
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xc5b43a…3867fc
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xe7449d…7bb4be
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xd0f15b…38a54d
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xc772dc…78bf64
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xb5406a…6e69bb
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams352d ago0xb100c3…3aa647
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams352d ago0x235b36…964c02
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams353d ago0x6d57d7…a05510
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams353d ago0x63e9ff…6b17ae
0x19ec…6a6f0x6482…b779BaseBase$0.0001100%daydreams353d ago0xbb8cd1…be26fa

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

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

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: 0x19ec…6a6f

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