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,400,982 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%daydreams323d ago0x8bf617…5cff42
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams323d ago0xd1f665…32b0f2
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams323d ago0xda0854…ca466c
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams323d ago0x7f4133…2d7137
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams323d ago0x79e85e…344795
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams323d ago0x94ad29…33de50
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams323d ago0xb329a2…67add4
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams324d ago0xd77831…7d8e99
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams324d ago0xc29b46…cdcc9c
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams324d ago0xc74705…3b7c1f
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams324d ago0x440b1d…fe7f95
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams324d ago0x2e54db…68e16e
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams324d ago0xd16b6c…7ea079
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams324d ago0x3f6891…da163b
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams324d ago0x12034b…cb21d8
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams324d ago0xc0c894…e31534
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams325d ago0xac3bf7…d36637
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams325d ago0xafddbe…95472b
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams325d ago0x53f12f…a332cb
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams325d ago0xc8acc2…a06433
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams325d ago0xa4b67c…4e5689
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams325d ago0x026c7c…b167dd
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams325d ago0x70fc55…f248f5
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams325d ago0xc97c5f…285647
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams325d ago0x2f550a…a5e666

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.