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.43M Roundhouse has indexed across 1,401,742 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%daydreams341d ago0x57a029…60abea
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams341d ago0xd6f578…a9e311
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams341d ago0x06e248…3db00d
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams341d ago0x3c4201…38a621
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams341d ago0x29ed5e…5dc44f
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams341d ago0x81ccaa…ea0121
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams342d ago0x342cb9…c36fa8
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams342d ago0x646fd6…46eaef
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams342d ago0xf70e29…68f098
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams342d ago0x0383b5…65b86a
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams342d ago0x47bf6e…a2bbc4
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams342d ago0x1c4e80…cdf38d
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams342d ago0xfc1b53…23263c
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams342d ago0xc5d155…022e41
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams342d ago0x06e238…ec58ef
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams342d ago0x4055e0…47dbfe
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams343d ago0x3db4c9…1c7d17
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams343d ago0x744031…05d986
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams343d ago0x5822e9…23ebed
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams343d ago0xf4a807…1f5c3d
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams343d ago0x678f62…407d9b
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams343d ago0x4350f9…6c0624
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams343d ago0x5f43a0…a1ddb2
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams343d ago0x9bcfc3…3e7fc4
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams343d ago0xcad057…99606a

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.