AgentReport

0x1ba7…9906

0x1ba75840392ac95d5ac53715aa9d594c3f769906Explorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
268
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 (268)

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

$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
    268 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.00268276d 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 268 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams325d ago0x977576…38d991
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams325d ago0x490ddd…76c718
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams326d ago0x119b8c…c8a98a
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams326d ago0xe44f78…aa1fb5
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams326d ago0xcc64a8…9bb9ca
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams326d ago0x796651…d3ffd0
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams326d ago0x0f2231…7ead87
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams326d ago0x6532d0…d6309f
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams326d ago0x4de2a7…4773a9
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams326d ago0x3ea304…8eec36
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams326d ago0xe6f105…f55569
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams327d ago0x988c3a…669bda
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams327d ago0x90c4b7…03bf96
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams327d ago0x868587…076fb0
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams327d ago0xf30fbe…41487c
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams327d ago0xb6a825…59cb7e
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams327d ago0x798210…5624d6
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams327d ago0x2388c5…59e68f
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams328d ago0xcb388e…6cf8c8
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams328d ago0x3a0179…141b3d
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams335d ago0x01e7a5…bfa4ab
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams337d ago0xf30080…7ca2f3
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams337d ago0x95c5fd…5710a6
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams337d ago0x86fed4…c3dbfd
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams337d ago0x3203f2…f98aa7

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

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

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: 0x1ba7…9906

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