AgentReport

0xb727…75cd

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

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

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

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

$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
    266 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.00266276d 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 266 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0xb4008d…10683c
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams343d ago0x779ff3…959e2d
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xe4d606…1d2bc8
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x55f395…619cde
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x5a2fdf…243ea7
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x05e16c…d0b850
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x2ccf60…f83995
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xcf992a…eb0c05
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x5ab183…8bb4e1
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x3557a9…978f5d
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0xff740f…f62b69
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams344d ago0x8db53d…f99ee9
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x14f2ea…41d593
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x7546b0…29909c
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x958347…0dbe6b
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x75e09f…436930
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x33d082…333b8c
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xef138f…0f8512
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xb1c67c…05809f
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xa40fbf…b77472
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x8885f6…adeb89
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xcba20c…895afa
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0x8e4803…b6e605
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams345d ago0xf2e6a8…61a308
0xb727…75cd0x6482…b779BaseBase$0.0001100%daydreams346d ago0x579414…7699bc

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

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

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: 0xb727…75cd

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