AgentReport

0x663f…fdf3

0x663fd025fa09b86ed07cb5b604388042ad4ffdf3
$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 58d 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.00158d agoGraph
0x8170…e743$0.00$0.02258d 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
0x663f…fdf30xd820…337cBase SepoliaBase Sepolia$0.0270%0xd407…f1bf58d ago0x357a02…8a26c0
0x8170…e7430x663f…fdf3Base SepoliaBase Sepolia$0.0170%0xd407…f1bf58d ago0x1dafe1…0e9d62
0x8170…e7430x663f…fdf3Base SepoliaBase Sepolia$0.0170%0xd407…f1bf58d ago0x5ce52d…8eb883

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

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

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: 0x663f…fdf3

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