AgentReport

0x273e…0335

0x273e2a5be6f5734666a84f9307c92c0bbb8c0335Explorer
Paid out
$722.45
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
26
Last 7d vs prior 7d
5
Distinct counterparties
Over the whole indexed history

Paid $722.45 of the $846.56M Roundhouse has indexed across 1,329,848 wallets — less than 0.0001% of it.

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

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

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

  • 0x8c29…1dd8 · last paid 437d ago
    $413.50
    7 calls

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

  • 0x4ee8…d68d · last paid 525d ago
    $168.00
    12 calls

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

  • 0x9889…f6c6 · last paid 456d ago
    $121.95
    5 calls

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

  • 0xabfa…bd7c · last paid 456d ago
    $14.00
    1 call

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

  • 0x4398…e4e6 · last paid 426d ago
    $5.00
    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

MayJunJulAugSepOct
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x8c29…1dd8$413.50$0.007437d agoGraph
0x4ee8…d68d$168.00$0.0012525d agoGraph
0x9889…f6c6$121.95$0.005456d agoGraph
0xabfa…bd7c$14.00$0.001456d agoGraph
0x4398…e4e6$5.00$0.001426d agoGraph

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

Data quality

57% of observed volume is with a single counterparty, in all 26 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x273e…03350x4ee8…d68dBase$6.5070%0xe890…f632535d ago0x72dec4…d68d04

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

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

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: 0x273e…0335

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