AgentReport

0x7375…d358

0x73759fb8e7529a4d872337201d12815713ffd358Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
259
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3066.17M Roundhouse has indexed across 1,400,092 wallets — less than 0.0001% of it.

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

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

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

  • 0x6482…b779 · last paid 276d ago
    $0.03
    259 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
0x6482…b779$0.03$0.00259276d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 259 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams323d ago0x26bbfa…7b9bb9
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams323d ago0x7c40ea…8a18a2
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams323d ago0x491505…4344e7
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams323d ago0x251b45…bf1682
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams323d ago0x481f72…9dc999
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams323d ago0xf9b881…b2d99c
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams323d ago0xf921c2…550bd6
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams324d ago0x278d96…f704e5
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams324d ago0x336102…ef8b9b
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams324d ago0x486f2a…a9b4c3
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams324d ago0x2e31bd…fbdf6a
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams324d ago0x707308…227597
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams324d ago0x8a3548…591817
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams324d ago0x794c5b…ec4ff1
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams324d ago0x638cf5…b91a7a
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams324d ago0x066436…e8b265
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams324d ago0xde3416…8d3d51
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams324d ago0xad9953…d6afec
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams325d ago0x2465d8…35fbf5
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams325d ago0x2f5ef9…b93cbb
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams325d ago0xfc1cd7…c92de9
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams325d ago0x186533…3b1745
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams325d ago0x489340…310b1b
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams325d ago0xc0e475…ee3223
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams325d ago0x21d022…af5459

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

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

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: 0x7375…d358

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