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.00M Roundhouse has indexed across 1,401,091 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%daydreams341d ago0x60e615…c3434e
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams341d ago0xc86d70…84c80f
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams342d ago0x18e439…a79f2d
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams342d ago0x04f049…9a1577
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams342d ago0x84c39c…74983c
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams342d ago0xbc8303…9e8c99
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams342d ago0x608649…97828c
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams342d ago0xefae03…d5f507
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams342d ago0x5560e9…afe1d0
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams342d ago0xf3193a…2730da
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams342d ago0x62d621…1b5d0e
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams342d ago0x668415…a23478
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams342d ago0xa7b4c1…681baf
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams343d ago0xf83299…2d848f
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams343d ago0xb3139d…6144ca
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams343d ago0x49d469…7a8b9d
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams343d ago0xb35931…28873f
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams343d ago0x9c7218…959e6e
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams343d ago0x32f7af…c01568
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams343d ago0x76c7f6…2b8bab
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams343d ago0xe30cc8…8c8cbc
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams343d ago0x2ac4a6…d28cd6
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams343d ago0x7e3804…7ba6d6
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams344d ago0x16b5f9…e25ebc
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams344d ago0x37bc03…647f24

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.