AgentReport

0xe00f…cd17

0xe00ffbed0fefc0cbba8856627a76726af236cd17Explorer
Paid out
$0.81↓ 18%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
812↓ 18%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.81 of the $3069.68M Roundhouse has indexed across 1,403,034 wallets — less than 0.0001% of it.

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

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

$0.81 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 13m ago
    $0.65
    648 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.16
    164 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.65$0.0064813m agoGraph
0x9c95…e299$0.16$0.00164113d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x022c34…373768
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x7aa6ae…96e422
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x0b2d1f…36637b
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x91148f…958682
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0xb06694…a16ba6
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x2ee77a…e09675
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0xb1db44…82530d
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0xe96d15…6845bd
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x5f7a40…fd20e5
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x982338…909712
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x26d6f1…431347
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x36fb77…b96a9d
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x1d9cb8…5abac8
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0xc21e10…2a2ea5
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0xaf125d…36a380
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x3030e9…24b207
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x86ef16…a24c4a
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x6c8905…6da2d3
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x86282e…2ca01a
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x0beb41…092d11
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x0d3f4a…5f877e
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x8412ef…46f792
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0xe66733…6d3689
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x4a6670…ccf94a
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa11d ago0x43b906…62904d

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

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

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: 0xe00f…cd17

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