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,401,091 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%daydreams337d ago0xdce797…e38471
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams337d ago0x9d0880…10ec43
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams338d ago0x360491…9e2a35
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams338d ago0xd4eb1d…bba502
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams338d ago0x5939d5…8097d6
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams338d ago0xead811…e48346
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams338d ago0xa3b035…74efea
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams339d ago0x3864bb…be17ea
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams339d ago0x58efa4…73f8d3
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams339d ago0xb81b47…eade38
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams339d ago0x07f463…d26f7f
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams339d ago0xb84ea1…0c7f07
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams340d ago0xb82eef…d6768e
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams340d ago0x5a8a06…5288f1
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams340d ago0x871a64…5d9c0f
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams340d ago0x3749da…09d59f
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams340d ago0x3b5bef…377c3c
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams340d ago0xb7f92f…984200
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams340d ago0x56ecdc…5be49f
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams340d ago0x31fd33…75f728
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams340d ago0xff38fe…b0db53
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams340d ago0xfdd9f3…6e8af6
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams341d ago0xa62db2…c37a6f
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams341d ago0x2ece66…856384
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams341d ago0xc126e2…a4d174

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.