AgentReport

0x4a5b…d3bd

0x4a5b72e3d2f74c9f9555916eb59ba36248a9d3bdExplorer
$0.00777
Paid out
$0.00
Received
4
Settlements
2
Distinct counterparties
Over the whole indexed history

Paid $0.00777 of the $260.92M Roundhouse has indexed across 716,778 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.0077742

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

  • 0x94d0…f73c · last paid 326d ago
    $0.006282
    1 call

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

  • 0x26b5…97d9api.questflow.aiEndpoint up
    0x26b5…97d9 · last paid 326d ago
    $0.001488
    3 calls
    ▸1 catalogued endpoints, none priced at an amount this agent paid
Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

Activity

MarAprMayJunJulAugSep
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x94d0…f73c$0.006282$0.001326d agoGraph
0x26b5…97d9$0.001488$0.003326d agoGraph

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

Data quality

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

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x4a5b…d3bd0x26b5…97d9Base$0.000843100%questflow326d ago0x823860…3c8b2a
0x4a5b…d3bd0x94d0…f73cBase$0.006282100%questflow326d ago0x633878…9d567a
0x4a5b…d3bd0x26b5…97d9Base$0.000314100%questflow326d ago0xb32f88…a84f6b
0x4a5b…d3bd0x26b5…97d9Base$0.000331100%questflow326d ago0x3050ac…d2707a

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

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

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: 0x4a5b…d3bd

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