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%daydreams343d ago0x494be8…a78ea4
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams343d ago0xc490f2…7fab9b
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams343d ago0xa8593e…63871d
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams343d ago0xc834da…59c3af
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams343d ago0xa432d1…419f38
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams343d ago0x8b4a8e…b99f31
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams343d ago0x82119f…d35b6b
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams344d ago0x0443a3…22c6f8
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams344d ago0x878231…243801
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams344d ago0x95f181…043524
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams344d ago0x5f14bf…0cd576
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams344d ago0xa3fd1d…8c9295
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams344d ago0x75f28d…297148
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams344d ago0xc1dbbd…e1d3e8
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams344d ago0xffa946…2c1682
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams344d ago0xafb34e…28a9db
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams344d ago0x085c96…92bcb9
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams344d ago0x8481c7…e3ed36
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams345d ago0x8052e0…e9c68f
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams345d ago0xf547b1…13ef3b
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams345d ago0x282e8f…eae753
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams345d ago0x91a00d…9d6a58
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams345d ago0x15f3e9…28714c
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams345d ago0x745fdc…559b8a
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams345d ago0x9fe97c…0c18a1

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.