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,575 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%daydreams353d ago0xdcbcff…8efb80
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams353d ago0x249e0b…d07b30
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams353d ago0xd1dd70…4422c5
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams353d ago0xab2d00…bd8510
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams353d ago0x2d8cae…fe9e80
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams354d ago0x534903…c01a29
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams354d ago0x62f643…03efeb
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams355d ago0x474523…91a00d
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams355d ago0x610cbb…72d10a
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams355d ago0x304ccc…e3478c
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams355d ago0x8dd546…7d8311
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams355d ago0x1f4f0a…9a2bdc
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams355d ago0x43d2dc…7ee872
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams356d ago0x316bdb…152c37
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams356d ago0x446ded…4eed55
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams356d ago0x683e91…51b336
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams356d ago0x659d07…1ee823
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams356d ago0x9b8b04…81e610
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams356d ago0x376786…f4fce9
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams357d ago0xed6030…7da645
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams357d ago0x6b7f78…0f4600
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams357d ago0x79506d…25daa7
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams357d ago0xadb201…b8e175
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams358d ago0xb360b5…92717d
0x7b1d…75f10x6482…b779BaseBase$0.0001100%daydreams358d ago0x8d6f5c…4403fa

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.