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,510 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%daydreams345d ago0xe017c8…8ad739
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams345d ago0xcbc8c4…f624f4
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams345d ago0x6ee24b…d1155b
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams345d ago0x6a24b0…284b06
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams345d ago0x1f15b3…b7c338
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams346d ago0x76bac6…3d861a
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams346d ago0xcc19fa…69613a
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams346d ago0x4b2255…d559c4
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams346d ago0x9ad211…6f0cd9
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams346d ago0x4dd7f5…3a1be2
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams346d ago0x1eb88d…a9dc7d
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams346d ago0xee7352…03e5f3
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams346d ago0x3bd873…f0cacf
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams346d ago0xb4d45c…4b2253
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams346d ago0x9cc879…065b34
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams346d ago0xf5a037…f29793
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams347d ago0xfaff36…18fc4d
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams347d ago0x389d3f…f80bfb
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams347d ago0x916f49…0eb18e
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams347d ago0x4178b0…807146
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams347d ago0x8785c9…586ace
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams348d ago0x539afa…b17483
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams348d ago0xb185f9…171213
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams348d ago0x77b9e0…fde97c
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams348d ago0x838fea…a7c6d0

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.