AgentReport

0x7b1d…75f1

0x7b1dfea891fd121bde7c64736cc9525c5c7e75f1Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
262
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,367 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (262)

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.032621

$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
    262 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.00262276d 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 262 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams348d ago0x1602f9…7f399a
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams348d ago0x40bee9…f6928b
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams349d ago0xa895f3…3a708d
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams349d ago0x183c8c…ad60af
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams350d ago0xffbed8…3183ec
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams350d ago0x6933ab…b06964
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams350d ago0x2f2762…aa9cea
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams350d ago0xe26897…5357f7
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams350d ago0x5509d1…7872bc
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams351d ago0x2c25b6…d4e9c8
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams351d ago0x698a7d…6d410a
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams351d ago0xf062a2…85e8ad
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams351d ago0x3a2baf…a6de65
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams351d ago0xcee766…08b767
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams351d ago0xa4ed8a…029ade
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams351d ago0x55992c…a9bd40
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams352d ago0xe03b1f…8bc7a2
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams352d ago0x97ee36…e69a15
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams352d ago0x27eae3…0d6374
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams352d ago0x86ce09…a749ad
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams352d ago0x6d84ce…fa638d
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams352d ago0xe28a92…a0dda6
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams352d ago0x20fc11…04dd6d
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams352d ago0xcbb01c…cfbd72
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams353d ago0x039260…80c622

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 0x7b1d…75f1 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x7b1dfea891fd121bde7c64736cc9525c5c7e75f1

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: 0x7b1d…75f1

curl -s 'https://api.roundhouseai.io/v0/agents/0x7b1dfea891fd121bde7c64736cc9525c5c7e75f1'
curl -s 'https://api.roundhouseai.io/v0/entities/0x7b1dfea891fd121bde7c64736cc9525c5c7e75f1/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.