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,575 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%daydreams349d ago0x4ffd5c…0bef4e
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams350d ago0x57adaa…c7d897
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams350d ago0xd15569…9abd06
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams350d ago0x63d865…fd3c02
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams350d ago0x06a7c6…52620c
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams350d ago0x9e15b4…5a904c
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams350d ago0x8ea3cf…72f4ab
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams351d ago0x867a06…0f80a9
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams351d ago0x5e47a7…4d8025
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams351d ago0x34d47f…772622
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams351d ago0xc91fdc…5f9524
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams351d ago0x526625…154fd3
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams351d ago0x292103…4640f7
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams351d ago0x6e0013…b01b58
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams351d ago0x3c0fe1…fe8b78
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams352d ago0x355041…2ff820
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams352d ago0x262887…f96e8d
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams352d ago0xcbe301…aca1b4
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams352d ago0x0747cc…2f25ad
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams352d ago0xae41a4…8f2e96
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams352d ago0x0001bb…b17538
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams352d ago0x33a3bd…26a7a9
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams352d ago0x3718bd…a2cb82
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams353d ago0xb67859…dcd2de
0x40fa…71860x6482…b779BaseBase$0.0001100%daydreams353d ago0x0ffbda…3bf34a

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.