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,255 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%daydreams337d ago0x3ac704…554ff7
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams337d ago0xc5453c…34b665
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams337d ago0x26fc23…d552a5
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams337d ago0xcf7fa7…a95a06
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams337d ago0x4a98d6…e939a9
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams338d ago0x870c56…7e253e
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams338d ago0xe71069…5909ff
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams339d ago0x37c393…c5ed76
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams339d ago0x080ea6…e2426e
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams339d ago0x3d63a6…e15aa1
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams339d ago0x4d103e…14ab77
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams339d ago0x87cdb0…74f866
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams339d ago0xb2a32a…b16274
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams339d ago0xa9a8bb…180717
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams340d ago0xf5105b…ff3537
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams340d ago0xec3823…43ac85
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams340d ago0xd52928…b9490e
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams340d ago0xc57b92…786f0a
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams340d ago0x8c4527…b4418b
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams340d ago0xef3a6d…922af1
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams340d ago0xa88f14…6c7311
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams340d ago0x917131…c18dd4
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams340d ago0x5754fd…7f35b2
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams340d ago0x70aea2…b20f55
0x7375…d3580x6482…b779BaseBase$0.0001100%daydreams340d ago0xb303bf…ab29b7

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.