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%daydreams325d ago0x03daf0…583770
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams326d ago0xd25604…fba65f
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams326d ago0x0aeb01…d55bff
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams326d ago0x7a4fb4…468730
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams326d ago0x6b670e…4b6265
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams326d ago0xb3b311…8fc43a
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams326d ago0x91a40b…066015
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams326d ago0x46eef7…459975
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams326d ago0xd9b2da…a0b40d
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams326d ago0xc00539…dff849
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams326d ago0x402f44…c85211
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams326d ago0xdfa475…f9e868
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams327d ago0x8cbfc7…ac3c29
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams327d ago0x12fbcf…b219f9
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams327d ago0x0e474d…db08c6
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams327d ago0x56b4a6…941842
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams327d ago0xb95563…eb8c2f
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams327d ago0x3d1c39…2ff1dd
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams327d ago0xfbc8b7…6c1392
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams327d ago0xe66356…cd7bd7
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams328d ago0x12849c…10f4a4
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams335d ago0x25ab9f…6ae6cc
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams337d ago0x64a6c3…b7ef56
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams337d ago0x81d075…2fb5d8
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams337d ago0x2369b9…2c735f

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.