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%daydreams352d ago0x3e6e74…ed6d40
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams352d ago0x1d021b…77f9ad
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams352d ago0x71dc8e…bffbb9
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams352d ago0x82f1fb…f6fb61
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams353d ago0x847a49…d7d418
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams353d ago0xccafc6…09ba2b
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams353d ago0x2c961b…9f5571
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams353d ago0x198e32…8070a8
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams353d ago0x9ebe0b…58c437
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams353d ago0x64571a…88eaf0
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams354d ago0x353ef9…b2332b
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams354d ago0x3cb8cb…a2736d
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams355d ago0x5be148…9d09ec
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams355d ago0x65bb2e…a48afc
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams355d ago0xb66017…a3746d
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams356d ago0x685763…a9f2ec
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams356d ago0x55475d…2be174
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams356d ago0x3ded34…2a8f7f
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams356d ago0x953ada…983c2b
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams356d ago0x89665d…d0c66a
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams357d ago0xce70f6…0cdbf8
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams357d ago0xf0fd46…5c70d3
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams357d ago0x08236f…7751db
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams358d ago0x54e235…43834e
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams358d ago0x05f8c5…1dacfc

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.