AgentReport

0xed1b…2a4a

0xed1b1d9208befc606070c9fdb2b7e7b4d02d2a4aExplorer
Paid out
$0.001
Last 7d vs prior 7d
Received
$0.002
Last 7d vs prior 7d
Settlements
3
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.001 of the $259.00M Roundhouse has indexed across 713,892 walletsless than 0.0001% of it.

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

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

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

  • 0x244f…cab9 · last paid 87d ago
    $0.001
    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
0xd3df…7bd2$0.00$0.002224d agoGraph
0x244f…cab9$0.001$0.00187d agoGraph

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

Data quality

67% of observed volume is with a single counterparty, in all 3 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xd3df…7bd20xed1b…2a4aBase$0.001100%fluxa24d ago0xadb27b…8e6a97
0xed1b…2a4a0x244f…cab9Base$0.001100%fluxa87d ago0x60189c…9d35ef
0xd3df…7bd20xed1b…2a4aBase$0.001100%fluxa87d ago0x154862…4c1384

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

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

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: 0xed1b…2a4a

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