AgentReport

0xab4a…d664

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

Paid $0.000958 of the $260.63M Roundhouse has indexed across 716,280 wallets — less than 0.0001% of it.

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

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

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

  • 0x507f…6dbd · last paid 306d ago
    $0.000584
    2 calls

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

  • 0x4944…4bf3 · last paid 306d ago
    $0.000374
    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

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x507f…6dbd$0.000584$0.002306d agoGraph
0x4944…4bf3$0.000374$0.002306d agoGraph

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

Data quality

61% of observed volume is with a single counterparty, in all 4 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xab4a…d6640x4944…4bf3Base$0.000182100%questflow306d ago0xa94677…225f4e
0xab4a…d6640x507f…6dbdBase$0.000285100%questflow306d ago0xb81c36…7d43f8
0xab4a…d6640x507f…6dbdBase$0.000299100%questflow317d ago0x10ea9c…3a8b49
0xab4a…d6640x4944…4bf3Base$0.000192100%questflow317d ago0x250931…483a52

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

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

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: 0xab4a…d664

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