AgentReport

0x6da8…afa5

0x6da822f8ddb1e0746e5b10f3f236e26d6238afa5Explorer
Paid out
$0.02
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.02 of the $842.27M Roundhouse has indexed across 1,319,547 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.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.

  • 0x3577…ca8d · last paid 19d 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…

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.02$0.00119d agoGraph
0x1f00…099b$0.00$0.0120323d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x6da8…afa50x3577…ca8dBase$0.0270%0x642b…6c7519d ago0x58a52f…1b2a50
0x1f00…099b0x6da8…afa5Base$0.006319100%questflow323d ago0x4f6a22…e99198
0x1f00…099b0x6da8…afa5Base$0.000076100%questflow326d ago0x946847…e89bae
0x1f00…099b0x6da8…afa5Base$0.000067100%questflow327d ago0x8a6ec9…d14289
0x1f00…099b0x6da8…afa5Base$0.000052100%questflow330d ago0x0a2c57…d14330
0x1f00…099b0x6da8…afa5Base$0.000058100%questflow331d ago0x72d823…c6f9fd
0x1f00…099b0x6da8…afa5Base$0.000096100%questflow332d ago0x575af6…2cbc04
0x1f00…099b0x6da8…afa5Base$0.000082100%questflow334d ago0xc2b4b8…ad4d70
0x1f00…099b0x6da8…afa5Base$0.000195100%questflow335d ago0xbc9096…1cdff4
0x1f00…099b0x6da8…afa5Base$0.000455100%questflow338d ago0xea523c…dc568b
0x1f00…099b0x6da8…afa5Base$0.000421100%questflow339d ago0x140831…ea8e8a
0x1f00…099b0x6da8…afa5Base$0.000372100%questflow340d ago0x2de0f3…8aa101
0x1f00…099b0x6da8…afa5Base$0.000338100%questflow341d ago0x6994e1…f89670
0x1f00…099b0x6da8…afa5Base$0.000207100%questflow343d ago0x00a727…917de0
0x1f00…099b0x6da8…afa5Base$0.00051100%questflow344d ago0x6e42f5…4a983e
0x1f00…099b0x6da8…afa5Base$0.000186100%questflow345d ago0xc689eb…33aaf5
0x1f00…099b0x6da8…afa5Base$0.000303100%questflow346d ago0xef79d3…4a5fca
0x1f00…099b0x6da8…afa5Base$0.000433100%questflow347d ago0x8649ad…65c2a6
0x1f00…099b0x6da8…afa5Base$0.000228100%questflow348d ago0x0c8aef…551cbc
0x1f00…099b0x6da8…afa5Base$0.000272100%questflow350d ago0x56ef88…151604
0x1f00…099b0x6da8…afa5Base$0.000186100%questflow351d ago0x14d73c…17ddcb

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

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

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: 0x6da8…afa5

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