AgentReport

0xe073…42f4

0xe0734b79e62c97d3342e62a0303d29e55ced42f4Explorer
Paid out
$80,172.17
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
28
Last 7d vs prior 7d
5
Distinct counterparties
Over the whole indexed history

Paid $80,172.17 of the $834.22M Roundhouse has indexed across 1,300,907 wallets — 0.0096% of it.

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

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%$80,172.17285

$80,172.17 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.

  • 0x0f57…991f · last paid 445d ago
    $41,412.01
    2 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x9918…143e · last paid 416d ago
    $35,752.08
    6 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x416f…b72a · last paid 446d ago
    $2,233.93
    3 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x6b57…42cc · last paid 419d ago
    $674.13
    15 calls

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x7a44…4f20 · last paid 422d ago
    $100.02
    2 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

AprMayJunJulAugSepOct
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x0f57…991f$41,412.01$0.002445d agoGraph
0x9918…143e$35,752.08$0.006416d agoGraph
0x416f…b72a$2,233.93$0.003446d agoGraph
0x6b57…42cc$674.13$0.0015419d agoGraph
0x7a44…4f20$100.02$0.002422d agoGraph

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

Data quality

52% of observed volume is with a single counterparty, in all 28 observed settlements.

Recent activity

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

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

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: 0xe073…42f4

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