AgentReport

0xe00f…cd17

0xe00ffbed0fefc0cbba8856627a76726af236cd17Explorer
Paid out
$0.81↓ 18%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
811↓ 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 (811)

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

$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 2h ago
    $0.65
    647 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.006472h 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 811 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0xd410c0…f0565b
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x600377…cc6f76
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x2b76fb…1208eb
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0xbc3e19…728072
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0xaf51fc…01d738
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x7e196c…b107f0
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x05c0c0…86e4aa
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x003aad…2e48fd
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0xd39285…5d3a09
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0xf489b7…00f52f
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x7a77ed…d6784a
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0xab816c…ea3bd9
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x1abee5…7ff56e
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x1cd0ee…f6d6ef
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x3bc3c2…a7bb83
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x936056…93b2f5
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x4435d8…ccf37f
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x7f122a…6aecc1
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x92800f…1f45fc
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x7a554c…df1885
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x5467c6…131dce
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0xa1bcbc…6843f4
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0xa32457…0942d2
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x1f5f87…3b4ca7
0xe00f…cd170xfe80…47eeBaseBase$0.001100%fluxa10d ago0x022c34…373768

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.