AgentReport

0xf394…3563

0xf39473d1ad66128f2d0117f6fab1942f9e7c3563Explorer
Paid out
$0.90↑ 15%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
897↑ 15%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.90 of the $3105.74M Roundhouse has indexed across 1,407,824 wallets — less than 0.0001% of it.

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

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

$0.90 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 30m ago
    $0.70
    700 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 113d ago
    $0.20
    197 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.70$0.0070030m agoGraph
0x9c95…e299$0.20$0.00197113d agoGraph

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

Data quality

78% of observed volume is with a single counterparty, in all 897 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa15h ago0x72f737…18f6bb
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa16h ago0x139be7…eaf28c
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa17h ago0x0ca894…5b3fe2
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa17h ago0xe655a7…23b532
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa18h ago0xc6030b…6b7782
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa18h ago0xe6b8e2…78019d
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa19h ago0x8401bf…4f64ce
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa19h ago0x3ff220…402b52
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa20h ago0xc0a81a…0855f0
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa20h ago0x1acf8a…e8ea70
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa21h ago0x56f53d…6fa14d
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa21h ago0x893083…10864a
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa22h ago0xce549a…d97931
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa22h ago0x884e5d…2823ef
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa23h ago0x502e48…afb572
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa1d ago0xe64170…919627
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa1d ago0xd957b9…d2d23d
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa1d ago0x7ad8ec…7eee8b
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa1d ago0xbb949f…359997
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa1d ago0x4a074d…08642e
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa1d ago0x2df468…116aef
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa1d ago0x0d7dd5…388fed
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa1d ago0x20ed33…39c9a5
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa1d ago0x6cb962…36c255
0xf394…35630xfe80…47eeBaseBase$0.001100%fluxa1d ago0x316c8d…6a9610

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

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

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: 0xf394…3563

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