AgentReport

0x49c7…d75d

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

Paid $1.00 of the $846.70M Roundhouse has indexed across 1,330,126 wallets — less than 0.0001% of it.

Chains (from the recent scan): Base (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%$1.0022

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

  • 0x3b48…513c · last paid 493d ago
    $0.99
    1 call

    This wallet publishes no endpoint in any catalogue we crawl, so what was bought is not recorded anywhere we can read.

  • 0x1223…9e0fsnack.moneyEndpoint down
    0x1223…9e0f · last paid 495d ago
    $0.01
    1 call
    ▸1 catalogued endpoints, none priced at an amount this agent paid
    • /$0.02 listed
Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Funds flow over time

Activity

MayJunJulAugSepOct
LessMore

One square per day; click a day to see its settlements in the ledger.

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x3b48…513c$0.99$0.001493d agoGraph
0x1223…9e0f$0.01$0.001495d agoGraph

Ranked by settled amount over this wallet's recent settlement window — who it normally transacts with.

Data quality

99% of observed volume is with a single counterparty, in all 2 observed settlements.

Organic volume $1.00 of $1.00 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x49c7…d75d0x3b48…513cBase$0.9970%0x40a6…5eda493d ago0x2c3499…6811ee
0x49c7…d75d0x1223…9e0fBase$0.0150%0x40a6…5eda495d ago0x85c759…b69ab5

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

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

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: 0x49c7…d75d

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