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%daydreams346d ago0x0c0c48…a2eaf6
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams346d ago0x5f72e7…cf0caf
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams346d ago0x0ddaf9…617d72
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams346d ago0x25c555…2dad74
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams346d ago0xe7e101…72d397
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams346d ago0x96ef55…5e4338
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams346d ago0x303f50…ebb3ed
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams346d ago0xead222…f4ae6b
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams346d ago0x47f75e…005f21
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams347d ago0x2ef097…c4f205
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams347d ago0x02c8cf…822cd6
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams347d ago0xaaa74d…51ed0c
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams347d ago0x489dac…117a7e
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams347d ago0x906022…b9ab0d
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams348d ago0x92b407…bac862
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams348d ago0x538668…62d226
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams348d ago0xfe137e…1e0b56
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams348d ago0x3fedc4…f9d1a7
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams348d ago0x75b1a2…1b0929
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams348d ago0x3def1e…ad4fad
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams348d ago0xf07174…372b37
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams348d ago0x36c783…6dea8d
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams348d ago0x393df1…c48107
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams348d ago0x0c934f…5ba180
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams348d ago0x450174…b2bfde

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.