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%daydreams348d ago0x2c6b06…391d6b
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams349d ago0x6c742e…6732a7
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams349d ago0xc9efeb…e695a4
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams349d ago0x6587c7…27eec3
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams349d ago0xa50bbe…184146
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams349d ago0xb0f1c3…63e43d
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams349d ago0x2e387c…96ba70
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams349d ago0x14f2d4…cbec4d
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams349d ago0x739a69…2f01e0
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams350d ago0xae7d65…e18962
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams350d ago0xf21226…aa9807
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams350d ago0x149636…0734ce
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams351d ago0xf1c98c…44ed56
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams351d ago0xf878d0…e23c79
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams351d ago0xdcb89a…9ad9fb
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams351d ago0xa5d2bd…63a4e3
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams351d ago0xf40868…72d285
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams351d ago0x321eda…8fba94
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams351d ago0x7a3724…f9a929
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams352d ago0xaa552c…3f14b8
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams352d ago0x198b9b…b5e224
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams352d ago0xaf47fb…80ceb5
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams352d ago0x13c587…ba7d09
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams352d ago0xf41345…0bfc63
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams352d ago0xc60cf7…16fd0d

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.