AgentReport

0x97b3…f16c

0x97b3eaff74384f66b62d9b87ca0a819e3768f16cExplorer
Paid out
$0.01
Last 7d vs prior 7d
Received
$0.01
Last 7d vs prior 7d
Settlements
21
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.01 of the $839.90M Roundhouse has indexed across 1,313,103 wallets — less than 0.0001% of it.

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

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

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

  • 0x3577…ca8d · last paid 18d ago
    $0.01
    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…

Funds flow over time

Activity

AprMayJunJulAugSepOct
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x3577…ca8d$0.01$0.00118d agoGraph
0x3fd8…0f12$0.00$0.0120322d agoGraph

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

Data quality

52% of observed volume is with a single counterparty, in all 21 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x97b3…f16c0x3577…ca8dBase$0.0170%0x642b…6c7518d ago0x3cfa49…3a551c
0x3fd8…0f120x97b3…f16cBase$0.000313100%questflow322d ago0xb8ffa6…b39bdb
0x3fd8…0f120x97b3…f16cBase$0.005872100%questflow323d ago0x0a5ec9…9e2891
0x3fd8…0f120x97b3…f16cBase$0.000299100%questflow324d ago0x8ab6f3…58adbc
0x3fd8…0f120x97b3…f16cBase$0.00008100%questflow329d ago0x409e6e…25c1a4
0x3fd8…0f120x97b3…f16cBase$0.000059100%questflow329d ago0xeba43b…d4f4c7
0x3fd8…0f120x97b3…f16cBase$0.000069100%questflow330d ago0x76aa6a…87d091
0x3fd8…0f120x97b3…f16cBase$0.000054100%questflow331d ago0x453eca…dd1ada
0x3fd8…0f120x97b3…f16cBase$0.000078100%questflow332d ago0x817cd8…3dd370
0x3fd8…0f120x97b3…f16cBase$0.000046100%questflow334d ago0xf143d2…0c8995
0x3fd8…0f120x97b3…f16cBase$0.000446100%questflow337d ago0x746784…b8541a
0x3fd8…0f120x97b3…f16cBase$0.000398100%questflow338d ago0xa47dd2…5beeb0
0x3fd8…0f120x97b3…f16cBase$0.000358100%questflow339d ago0x5b1dde…986694
0x3fd8…0f120x97b3…f16cBase$0.000327100%questflow340d ago0xd201e7…3fa800
0x3fd8…0f120x97b3…f16cBase$0.000304100%questflow341d ago0xbcab2b…d7294a
0x3fd8…0f120x97b3…f16cBase$0.000207100%questflow342d ago0xde76ec…9e7243
0x3fd8…0f120x97b3…f16cBase$0.000341100%questflow343d ago0xd6b415…76254f
0x3fd8…0f120x97b3…f16cBase$0.000294100%questflow344d ago0xdab3f9…f976f1
0x3fd8…0f120x97b3…f16cBase$0.000212100%questflow346d ago0x2c0df4…47a113
0x3fd8…0f120x97b3…f16cBase$0.000308100%questflow348d ago0xb2d162…f6c56f
0x3fd8…0f120x97b3…f16cBase$0.000319100%questflow350d ago0x5707b3…baa52c

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

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

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: 0x97b3…f16c

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