AgentReport

0x6fc8…eee0

0x6fc8e068a1a7f678e6d05cfd9e5372085714eee0
$0.02
Paid out
$0.02
Received
3
Settlements
2
Distinct counterparties
Over the whole indexed history

Paid $0.02 of the $716.75K Roundhouse has indexed across 25,164 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base Sepolia (3)

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

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

  • 0xd820…337c · last paid 57d ago
    $0.02
    1 call

    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…

Activity

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0xd820…337c$0.02$0.00157d agoGraph
0xde99…cf9f$0.00$0.02257d agoGraph

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

Data quality

50% of observed volume is with a single counterparty, in all 3 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x6fc8…eee00xd820…337cBase SepoliaBase Sepolia$0.0270%0xd407…f1bf57d ago0x676e7c…068b2c
0xde99…cf9f0x6fc8…eee0Base SepoliaBase Sepolia$0.0170%0xd407…f1bf57d ago0x26ef0d…953df2
0xde99…cf9f0x6fc8…eee0Base SepoliaBase Sepolia$0.0170%0xd407…f1bf57d ago0x30022f…50e8af

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

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

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: 0x6fc8…eee0

curl -s 'https://api.roundhouseai.io/v0/agents/0x6fc8e068a1a7f678e6d05cfd9e5372085714eee0'
curl -s 'https://api.roundhouseai.io/v0/entities/0x6fc8e068a1a7f678e6d05cfd9e5372085714eee0/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://preview.roundhouseai.io/dashboard/connections. If you have neither, ask before going further.

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