AgentReport

0xe279…d6a8

0xe27928d45b4e92f44b739aded3983d674c37d6a8Explorer
Paid out
$0.006
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
6
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.006 of the $3058.83M Roundhouse has indexed across 1,396,904 wallets — less than 0.0001% of it.

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

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

$0.001 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; for 1 of 2 the amount paid narrows the list to the ones listed at that price.

  • 0xd094…f014p01--test-402--bcdjt922dnwt.code.runEndpoint down
    0xd094…f014 · last paid 380d ago
    $0.005
    5 calls
    ▸1 of 1 catalogued endpoints list a price this agent paid
    • /payPrice match$0.001 listed
  • 0xfe12…0f81 · last paid 379d ago
    $0.001
    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
0xd094…f014$0.005$0.005380d agoGraph
0xfe12…0f81$0.001$0.001379d 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 6 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe279…d6a80xfe12…0f81BaseBase$0.001100%x402rs379d ago0x00080f…4ae6ca
0xe279…d6a80xd094…f014BaseBase$0.001100%payAI380d ago0x6ba746…72c3b2
0xe279…d6a80xd094…f014BaseBase$0.001100%payAI380d ago0xb8bd11…c716e3
0xe279…d6a80xd094…f014BaseBase$0.001100%payAI380d ago0x84c5cd…de2698
0xe279…d6a80xd094…f014BaseBase$0.001100%payAI380d ago0xf41c25…947b7e
0xe279…d6a80xd094…f014BaseBase$0.001100%payAI380d ago0x596dda…b799a0

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

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

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: 0xe279…d6a8

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