AgentReport

0x278e…9f95

0x278e37e9659372d2a3dd9bae60dcf957268a9f95Explorer
Paid out
$0.87↑ 51%
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
866↑ 51%
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.87 of the $3061.41M Roundhouse has indexed across 1,398,509 wallets — less than 0.0001% of it.

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

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

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

  • 0xfe80…47ee · last paid 4m ago
    $0.62
    620 calls

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

  • 0x9c95…e299 · last paid 121d ago
    $0.25
    246 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
0xfe80…47ee$0.62$0.006204m agoGraph
0x9c95…e299$0.25$0.00246121d agoGraph

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

Data quality

72% of observed volume is with a single counterparty, in all 866 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa9d ago0xba0098…c519da
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa9d ago0x635c1e…62375e
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0xa9dda5…11b433
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x413431…554d5b
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0xca8ef6…fec012
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x18e8aa…df7071
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x6a2066…b1e686
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x125b1b…a05974
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x7a127e…a3e114
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0xa6008a…dd8cb4
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x01df8a…d147c1
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x379f1e…cfbaf7
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x7569b2…b73962
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x2eb9e0…3ab393
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0xb5bb9d…24d07e
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x737c4a…79c7da
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x4db08b…65c715
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0xd774c4…2b614b
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x320c00…8a7d22
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x36fbbb…51c656
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x041135…58d54d
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x2ce181…bf1289
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x259d82…ce3a51
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0x1c1cb2…2fc880
0x278e…9f950xfe80…47eeBaseBase$0.001100%fluxa10d ago0xf5f0d5…1d33cc

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

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

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: 0x278e…9f95

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