AgentReport

0xfec6a6b3e04c0e74c06e3e6e33a3a9c36515a085

0xfec6a6b3e04c0e74c06e3e6e33a3a9c36515a085Explorer
Paid out
$1.72
Last 7d vs prior 7d
Received
$1.66
Last 7d vs prior 7d
Settlements
127
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $1.72 of the $259.51M Roundhouse has indexed across 714,874 wallets — less than 0.0001% of it.

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

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

$1.72 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.

  • 0xac65…4417 · last paid 112d ago
    $1.72
    36 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

MarAprMayJunJulAugSep
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xac65…4417$1.72$0.0036112d agoGraph
0xb90a…9ae4$0.00$1.6691112d agoGraph

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

Data quality

51% of observed volume is with a single counterparty, in all 127 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa112d ago0xb4aee0…9cb212
0xfec6…a0850xac65…4417Base$0.01100%fluxa112d ago0xb7e603…e9a794
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa112d ago0xdd5b8b…49266e
0xfec6…a0850xac65…4417Base$0.07100%fluxa112d ago0x581a57…07dc09
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa112d ago0xc6a31e…0f207d
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa112d ago0xb0a393…be068a
0xfec6…a0850xac65…4417Base$0.02100%fluxa112d ago0x383306…1594c1
0xb90a…9ae40xfec6…a085Base$0.05100%fluxa112d ago0x8df831…46ec8b
0xb90a…9ae40xfec6…a085Base$0.02100%fluxa112d ago0x8672c0…b32ac5
0xfec6…a0850xac65…4417Base$0.01100%fluxa112d ago0x728223…96e334
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa112d ago0x9d8322…befad7
0xfec6…a0850xac65…4417Base$0.51100%fluxa113d ago0x9791d6…ea3df6
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa113d ago0xdcc4ad…83794c
0xb90a…9ae40xfec6…a085Base$0.50100%fluxa113d ago0x91db0d…21b4c4
0xfec6…a0850xac65…4417Base$0.05100%fluxa113d ago0xa0c77e…3c6bb2
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa113d ago0xd107fa…23f712
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa113d ago0xe9fd76…9593a1
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa113d ago0x2155e0…57e78f
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa113d ago0x94ac39…fff848
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa113d ago0xc920a6…537f70
0xfec6…a0850xac65…4417Base$0.02100%fluxa113d ago0x94f5d8…c15197
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa113d ago0xde4a39…6b0548
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa113d ago0x8e2a31…2d8c1d
0xfec6…a0850xac65…4417Base$0.01100%fluxa113d ago0x096572…383aee
0xb90a…9ae40xfec6…a085Base$0.01100%fluxa114d ago0x6bee21…219c54

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

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

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: 0xfec6a6b3e04c0e74c06e3e6e33a3a9c36515a085

curl -s 'https://api.roundhouseai.io/v0/agents/0xfec6a6b3e04c0e74c06e3e6e33a3a9c36515a085'
curl -s 'https://api.roundhouseai.io/v0/entities/0xfec6a6b3e04c0e74c06e3e6e33a3a9c36515a085/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.