AgentReport

0x1309…04b0

0x130959631ec3346c78af495e7ba98abc86d504b0Explorer
Paid out
$0.02
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
246
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.02 of the $3067.84M Roundhouse has indexed across 1,401,919 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (246)

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.022461

$0.02 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.02
    246 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.02$0.00246276d 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 246 observed settlements.

Organic volume $0.02 of $0.02 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0x4df8f2…1d838f
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xd10ea7…b7b623
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0x63846d…767560
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0x42c50a…612b0d
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xa41530…18d5be
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams345d ago0xe73ea3…c60051
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams345d ago0xbd330e…7b3eec
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x38fcba…304e7f
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x8abd2b…51b640
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams345d ago0xd69c8e…9c0d0e
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams345d ago0xea9e1a…687da0
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x8487cb…8cc5d9
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams345d ago0x5d5dd0…fc0077
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams345d ago0xc5b005…0b6810
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams345d ago0xa29122…cb1ebb
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams345d ago0xb6d416…43fbca
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x990863…832dfc
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x9cfbbc…86d722
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x6cf53a…5899f2
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x1646eb…a82294
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x56540f…5518e9
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x56cd43…335ca4
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x681317…153640
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams346d ago0x5bec64…e5ee56
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams346d ago0xe3dfd4…d1483c

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 0x1309…04b0 has actually paid for over the free read API. No key, no account.

GET api.roundhouseai.io/v0/agents/0x130959631ec3346c78af495e7ba98abc86d504b0

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: 0x1309…04b0

curl -s 'https://api.roundhouseai.io/v0/agents/0x130959631ec3346c78af495e7ba98abc86d504b0'
curl -s 'https://api.roundhouseai.io/v0/entities/0x130959631ec3346c78af495e7ba98abc86d504b0/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.