AgentReport

0x40fa…7186

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

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,742 wallets — less than 0.0001% of it.

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

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.032561

$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 276d ago
    $0.03
    256 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.00256276d 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 256 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams353d ago0x108cd5…2f8230
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams353d ago0x128edd…6c58ff
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams353d ago0xca854d…88eaa1
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams353d ago0x47ff8f…7a1b88
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams355d ago0x2930c4…149f5a
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams355d ago0xa33e97…06e554
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams356d ago0x5bf83c…826dfc
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams356d ago0xd59228…047704
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams356d ago0x59866c…aac3eb
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams356d ago0x12934e…df67ba
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams356d ago0xa49265…b28598
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams357d ago0x9d36eb…c09260
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams357d ago0xce89b3…2b6a82
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams357d ago0x541da7…ea3184
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams357d ago0x63d000…35ebb9
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams358d ago0x6be35f…4aed92
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams359d ago0xefa3eb…d83b54
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams359d ago0x6c2e4a…a512d7
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams359d ago0x1e1e2b…df9dee
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams359d ago0x4201f1…8d822d
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams360d ago0xfc35a1…f2202b
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams360d ago0xf2878d…ee999b
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams361d ago0x316415…1eb219
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams361d ago0x1288fb…82b7d1
0x40fa…71860x6482…b779BaseBase$0.0001100%payAI361d ago0x33733a…89a9a3

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

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

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: 0x40fa…7186

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