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%daydreams342d ago0x34181a…5cf777
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams342d ago0xa03932…030ac3
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams342d ago0x5a267f…ec367e
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams342d ago0xec76b8…c314d0
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams342d ago0x00724f…f94567
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams342d ago0x0fe27b…cac81b
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams342d ago0xb5a176…7e87af
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams343d ago0xf753a0…9f06e2
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x48c48c…8186a3
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x324e3d…e23cac
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x26bf1f…915291
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x319bdf…6799e6
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams343d ago0xa7bb3a…db56b8
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x9193c3…bcf297
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams343d ago0xf5c6e9…d2171c
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x3f679a…2cd85b
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams343d ago0xd9f011…e2b7a6
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams343d ago0x157f84…fff5af
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xf73726…af2516
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0x030a78…0be20d
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xd50c5f…023ab8
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0x6eabad…2cf7fd
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xbf1b98…258717
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0xd3441c…92d749
0x1309…04b00x6482…b779BaseBase$0.0001100%daydreams344d ago0x2be1df…3f5648

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.