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.54M Roundhouse has indexed across 1,400,689 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%daydreams352d ago0x45f1d5…2a9f72
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams352d ago0xfe567c…2d4f0f
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams352d ago0x2f9e61…272b54
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams352d ago0x901d78…bdab5d
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams352d ago0xdec491…7c8576
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams352d ago0x7d7ec7…cc4393
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams352d ago0x77526d…870ca1
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams352d ago0x111b6f…7e9d78
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams353d ago0x38a799…5d5f09
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams353d ago0x06027c…416f5c
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams353d ago0xd59bff…a7d873
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams354d ago0x847502…077c6a
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams354d ago0xdcf031…142a55
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams354d ago0x02ad8b…38dd3a
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams354d ago0x561991…a5858b
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams355d ago0x6828e7…6d539d
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams355d ago0x3dd146…239862
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams355d ago0x162944…cb4af4
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams355d ago0xd47ead…f4993f
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams356d ago0x739bfb…cc8b5b
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams356d ago0xeafe62…4d91a7
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams356d ago0x5140f8…13a870
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams356d ago0xe7e9aa…c7ef7b
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams357d ago0x45671e…5165f1
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams357d ago0x2c2ba9…239bfe

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.