AgentReport

0xc02a…69e4

0xc02ad2805d28cc721f807dcc485e91a20f3669e4Explorer
Paid out
$0.54
Last 7d vs prior 7d
Received
$0.39
Last 7d vs prior 7d
Settlements
80
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.54 of the $3068.58M Roundhouse has indexed across 1,402,563 wallets — less than 0.0001% of it.

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

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

$0.54 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 37d ago
    $0.54
    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

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x3577…ca8d$0.54$0.00137d agoGraph
0xc492…e948$0.00$0.3979341d agoGraph

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

Data quality

58% of observed volume is with a single counterparty, in all 80 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc492…e9480xc02a…69e4BaseBase$0.01100%questflow357d ago0xa29be1…f33043
0xc492…e9480xc02a…69e4BaseBase$0.005831100%questflow357d ago0xe86026…19d512
0xc492…e9480xc02a…69e4BaseBase$0.002161100%questflow358d ago0x4c1626…d3766a
0xc492…e9480xc02a…69e4BaseBase$0.00041100%questflow358d ago0x67ddf1…cfd8dd
0xc492…e9480xc02a…69e4BaseBase$0.007248100%questflow358d ago0xbb271e…1cfe79
0xc492…e9480xc02a…69e4BaseBase$0.000411100%questflow359d ago0x9edeb5…94dee8
0xc492…e9480xc02a…69e4BaseBase$0.007273100%questflow359d ago0x401b83…3ff80b
0xc492…e9480xc02a…69e4BaseBase$0.007254100%questflow360d ago0x4bf3f5…4b18a8
0xc492…e9480xc02a…69e4BaseBase$0.000363100%questflow360d ago0x029bc9…700dcd
0xc492…e9480xc02a…69e4BaseBase$0.002334100%questflow361d ago0x763998…0d7a40
0xc492…e9480xc02a…69e4BaseBase$0.000396100%questflow361d ago0x6153f9…6e8fba
0xc492…e9480xc02a…69e4BaseBase$0.00721100%questflow363d ago0x14c761…8f424f
0xc492…e9480xc02a…69e4BaseBase$0.005134100%questflow363d ago0x288d2d…337e55
0xc492…e9480xc02a…69e4BaseBase$0.005526100%questflow363d ago0x286a0c…c46e3a
0xc492…e9480xc02a…69e4BaseBase$0.01100%questflow363d ago0xb76b5c…73d150
0xc492…e9480xc02a…69e4BaseBase$0.005649100%questflow363d ago0x77ee9d…ce5242
0xc492…e9480xc02a…69e4BaseBase$0.03100%questflow363d ago0xa8eb74…688363
0xc492…e9480xc02a…69e4BaseBase$0.004573100%questflow363d ago0xc91ff5…00ae83
0xc492…e9480xc02a…69e4BaseBase$0.000449100%questflow363d ago0x50a25c…638a1d
0xc492…e9480xc02a…69e4BaseBase$0.002095100%questflow363d ago0xe375be…468745
0xc492…e9480xc02a…69e4BaseBase$0.005514100%questflow363d ago0xc957b4…d4c0d2
0xc492…e9480xc02a…69e4BaseBase$0.000379100%questflow363d ago0x157c38…ebb13b
0xc492…e9480xc02a…69e4BaseBase$0.001322100%questflow363d ago0xb0068c…604716
0xc492…e9480xc02a…69e4BaseBase$0.001531100%questflow363d ago0x0d8b93…a00eb9
0xc492…e9480xc02a…69e4BaseBase$0.007881100%questflow363d ago0xa63c32…cfa148

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

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

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: 0xc02a…69e4

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