AgentReport

0x49a4383bc01d27e0fba71874d02a901d82a3add5

0x49a4383bc01d27e0fba71874d02a901d82a3add5Explorer
Paid out
$1.02
Last 7d vs prior 7d
Received
$0.56
Last 7d vs prior 7d
Settlements
2
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $1.02 of the $258.56M Roundhouse has indexed across 713,267 walletsless 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.0211

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

  • 0x858e…8a66 · last paid 115d ago
    $1.02
    1 call

    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

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x858e…8a66$1.02$0.001115d agoGraph
0xd1ae…8133$0.00$0.561118d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x49a4…add50x858e…8a66Base$1.02100%fluxa115d ago0x4480ec…329c43
0xd1ae…81330x49a4…add5Base$0.56100%fluxa118d ago0x42e9ca…0ef261

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

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

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: 0x49a4383bc01d27e0fba71874d02a901d82a3add5

curl -s 'https://api.roundhouseai.io/v0/agents/0x49a4383bc01d27e0fba71874d02a901d82a3add5'
curl -s 'https://api.roundhouseai.io/v0/entities/0x49a4383bc01d27e0fba71874d02a901d82a3add5/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.