AgentReport

0xe27d…0c77

0xe27d05b28abb404445d6d354d828762e03380c77Explorer
Paid out
$0.58
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
194
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.58 of the $3060.46M Roundhouse has indexed across 1,397,861 wallets — less than 0.0001% of it.

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

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

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

  • 0xb469…fe66 · last paid 260d ago
    $0.58
    194 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
0xb469…fe66$0.58$0.00194260d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 194 observed settlements.

Organic volume $0.58 of $0.58 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb337d ago0x840861…58a5b3
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb337d ago0x62f48f…ae85f7
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb337d ago0x5d3e9a…e8f0a8
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0x4887be…6fc47c
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0xc34574…27f475
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0x650674…077483
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0x5f7181…a798d8
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0x670672…0e9601
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0x7fa45b…855349
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0x7554a7…52824e
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0xbfd430…006169
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0x02c265…fe3b6c
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0x4805ef…d86d30
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0xf6b08b…f856fc
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0x73c7c3…cc5ab1
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb338d ago0x46cf1f…dae9f8
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb339d ago0x66cd86…fc7f5a
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb339d ago0x619395…3cd739
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb339d ago0xb953a4…febd54
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb339d ago0x76ec68…cda251
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb339d ago0x45f2ac…89860b
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb339d ago0x1d4564…efc8df
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb340d ago0x484f81…ba4285
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb340d ago0x916d01…833b94
0xe27d…0c770xb469…fe66BaseBase$0.002991100%thirdweb340d ago0x319e73…ade8d9

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

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

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: 0xe27d…0c77

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