AgentReport

0xf102…de90

0xf102cd92bc378df4a65569597b6d3ab077eede90Explorer
Paid out
$0.62
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
616
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.62 of the $3187.31M Roundhouse has indexed across 1,434,866 wallets — less than 0.0001% of it.

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

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

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

  • 0xfe80…47ee · last paid 64d ago
    $0.51
    506 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9c95…e299 · last paid 80d ago
    $0.11
    110 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
0xfe80…47ee$0.51$0.0050664d agoGraph
0x9c95…e299$0.11$0.0011080d agoGraph

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

Data quality

82% of observed volume is with a single counterparty, in all 616 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa68d ago0x9f4610…354458
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa68d ago0x811380…eaedd9
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa68d ago0x74ad8e…e67db1
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa68d ago0x774732…771c23
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa68d ago0xa7a852…ac8070
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa68d ago0xaebcf3…a0ff22
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa68d ago0x68c366…449660
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa68d ago0xf8dcf0…8c7331
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa68d ago0xaab03a…37c20c
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa68d ago0xe6974d…65b08a
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa68d ago0x5562a8…0d959e
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa70d ago0xc62aa9…8e0dec
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa70d ago0x4e1310…6c8377
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa70d ago0x1d57dd…ad2be7
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa70d ago0x31cfb9…2e7720
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa71d ago0xe883d0…56de5e
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa71d ago0x18bc4c…75c686
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa71d ago0x9c5259…9bfc26
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa71d ago0x3b4693…ac908b
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa71d ago0xf52502…3e0372
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa71d ago0xf66218…22d5db
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa71d ago0x72659b…233502
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa71d ago0x44b8b4…13acb2
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa71d ago0x297588…c9d197
0xf102…de900xfe80…47eeBaseBase$0.001100%fluxa71d ago0x571eef…effe52

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

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

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: 0xf102…de90

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