AgentReport

0xea9f…e869

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

Paid $225.75 of the $3067.00M Roundhouse has indexed across 1,401,091 wallets — less than 0.0001% of it.

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

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%$225.75182

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

  • 0x47c5…4fc3 · last paid 14d ago
    $154.35
    11 calls

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

  • 0x0e3d…7757 · last paid 88d ago
    $71.40
    7 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

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x47c5…4fc3$154.35$0.001114d agoGraph
0x0e3d…7757$71.40$0.00788d agoGraph

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

Data quality

68% of observed volume is with a single counterparty, in all 18 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xea9f…e8690x47c5…4fc3BaseBase$16.8070%0x705f…8eed14d ago0xe9fb6c…5a205b
0xea9f…e8690x47c5…4fc3BaseBase$11.5570%0x44e3…343221d ago0xbe9b05…6f017f
0xea9f…e8690x47c5…4fc3BaseBase$16.8070%0x12ba…6b6123d ago0xa11bc2…e9fe66
0xea9f…e8690x47c5…4fc3BaseBase$10.5070%0x1763…dc2225d ago0xdfe88f…389e36
0xea9f…e8690x47c5…4fc3BaseBase$10.5070%0x6bac…5e9b33d ago0xa47be4…56ae58
0xea9f…e8690x47c5…4fc3BaseBase$10.5070%0xedfa…1e1244d ago0xa97d73…a74117
0xea9f…e8690x47c5…4fc3BaseBase$10.5070%0xb7fe…9d8055d ago0xdbe0eb…ae83ba
0xea9f…e8690x47c5…4fc3BaseBase$28.3570%0x5047…e94073d ago0x685191…858be7
0xea9f…e8690x47c5…4fc3BaseBase$17.8570%0xd775…7f8187d ago0x793522…6af7c6
0xea9f…e8690x0e3d…7757BaseBase$1.0570%0x2d18…781188d ago0x1c230f…94e0e4
0xea9f…e8690x47c5…4fc3BaseBase$10.5070%0xaa2e…f04492d ago0x7c1b4b…8de075
0xea9f…e8690x47c5…4fc3BaseBase$10.5070%0x1f7e…db9697d ago0x5e7f10…e6b3c9
0xea9f…e8690x0e3d…7757BaseBase$9.4570%0x2d1c…632c104d ago0xb17ffd…c540da
0xea9f…e8690x0e3d…7757BaseBase$9.4570%0x6280…2e79109d ago0x9dcb32…4d1c7c
0xea9f…e8690x0e3d…7757BaseBase$7.3570%0x0744…c73c111d ago0x94a073…8c321b
0xea9f…e8690x0e3d…7757BaseBase$14.7070%0x1913…93d9119d ago0x2255bb…85cfd1
0xea9f…e8690x0e3d…7757BaseBase$1.0570%0xc22e…e4a1120d ago0xb609d3…5d183e
0xea9f…e8690x0e3d…7757BaseBase$28.3570%0x5dca…cd21165d ago0x24f128…893adf

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

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

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: 0xea9f…e869

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