AgentReport

0xc169…e3af

0xc169b5309e96dc5c4fabf639e1c2d3c8eeb5e3afExplorer
Paid out
$0.45
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
453
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.45 of the $3196.35M Roundhouse has indexed across 1,436,376 wallets — less than 0.0001% of it.

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

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

$0.45 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 41d ago
    $0.38
    376 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.08
    77 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.38$0.0037641d agoGraph
0x9c95…e299$0.08$0.007780d agoGraph

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

Data quality

83% of observed volume is with a single counterparty, in all 453 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x0214c2…7a34eb
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x88fb34…fd86c0
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0xcf1b18…5a4a5d
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x19387c…dafd49
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0xc0209e…88d04b
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x1a482e…89d6fe
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x47b5ba…8d0254
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0xd0beb0…48b40c
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x23fcaa…f6f85b
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x236b03…9e559b
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0xb258ce…18bdf8
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x176736…be6676
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x6ba68a…dbc7a0
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x070970…839205
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x66a01b…38b6bf
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x931f9c…b45c91
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x3cbbc5…b777c9
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x0ff2ac…c7b3de
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0xa7ad8d…1d6a83
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0xb94767…5c7de6
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x3f64eb…7ed5aa
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0xf3d4a7…f8a637
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0xd50219…102fcb
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x77a9f2…9ec844
0xc169…e3af0xfe80…47eeBaseBase$0.001100%fluxa68d ago0x92ec6f…f3f976

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

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

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: 0xc169…e3af

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