AgentReport

0x9454…3aa3

0x9454586b77963a03b4e5479338009d2046a43aa3Explorer
Paid out
$799.84
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
9
Last 7d vs prior 7d
5
Distinct counterparties
Over the whole indexed history

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

Chains (from the recent scan): Ethereum (9)

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
Onchain Data69%$549.8431
Not in any catalogue31%$250.0064

$250.00 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.

  • 0x0000…0000api.cleave.fiGas price?Endpoint up
    0x0000…0000 · last paid 237d ago
    $549.84
    3 calls
    ▸1 catalogued endpoints, none priced at an amount this agent paid
  • 0x4ef8…5148 · last paid 26d ago
    $119.97
    3 calls

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

  • 0xe973…0e71 · last paid 267d ago
    $95.00
    1 call

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

  • 0x3085…0197 · last paid 36d ago
    $30.03
    1 call

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

  • 0xc825…d17e · last paid 267d ago
    $5.00
    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
0x0000…0000$549.84$0.003237d agoGraph
0x4ef8…5148$119.97$0.00326d agoGraph
0xe973…0e71$95.00$0.001267d agoGraph
0x3085…0197$30.03$0.00136d agoGraph
0xc825…d17e$5.00$0.001267d agoGraph

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

Data quality

69% of observed volume is with a single counterparty, in all 9 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 0x9454…3aa3 has actually paid for over the free read API. No key, no account.

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

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: 0x9454…3aa3

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