AgentReport

0xf1d2…138b

0xf1d2f69cb584f7d87f21526d870552f89f68138bExplorer
Paid out
$198.63
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
2
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $198.63 of the $3063.39M Roundhouse has indexed across 1,398,970 wallets — less than 0.0001% of it.

Chains (from the recent scan): Ethereum (2)

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%$198.6321

$198.63 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.

  • 0x7dbb…59e0 · last paid 61d ago
    $198.63
    2 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
0x7dbb…59e0$198.63$0.00261d 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 2 observed settlements.

Organic volume $198.63 of $198.63 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf1d2…138b0x7dbb…59e0EthereumEthereum$183.6370%0x323a…a4f261d ago0xa80d99…82e46e
0xf1d2…138b0x7dbb…59e0EthereumEthereum$15.0070%0x323a…a4f261d ago0x3adb86…51579f

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

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

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: 0xf1d2…138b

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