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%daydreams343d ago0x19c167…fe834d
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams343d ago0xf83567…662400
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams344d ago0x8647a9…981ea7
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams344d ago0x72ff7f…802aef
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams344d ago0xa7e68f…1056da
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams344d ago0x5c98ac…6c14d6
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams344d ago0x7476b2…08a6bd
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams344d ago0x48afb8…7f5e39
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams344d ago0xd286f9…30d910
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams344d ago0xe6d2cd…39abcc
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams344d ago0x46df4c…8fe8be
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams344d ago0x24b187…ea5f70
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0x1beb4f…6e19cf
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0xa36109…727bf6
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0x92cb0b…60ddef
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0x4f7368…2b8979
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0x01e5ad…15c60e
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0x97c933…1e51ee
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0x6ac2bd…ef8d4c
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0xe21797…97e05c
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0xb7cdd5…ba33a7
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0x8b4108…765405
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0x9badde…bf81ef
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams345d ago0x2a7a11…282686
0x1ba7…99060x6482…b779BaseBase$0.0001100%daydreams346d ago0x6667d2…e23fe4

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.