AgentReport

0xa49e…fe34

0xa49e522e7368bcd1cf75ee2b3b9fb2641026fe34Explorer
Paid out
$1.58
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
1577
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $1.58 of the $3059.45M Roundhouse has indexed across 1,397,037 wallets — less than 0.0001% of it.

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

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%$1.001,0002

$1.00 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 37d ago
    $0.82
    818 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 76d ago
    $0.18
    182 calls

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

Folded from this wallet's 1,000 most recent settlements of 1,577 lifetime, which is as far back as one scan reaches — so every figure in this section is a floor, and the totals above are not.

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.82$0.0081837d agoGraph
0x9c95…e299$0.18$0.0018276d agoGraph

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

Data quality

82% of observed volume is with a single counterparty, in the 1000 most recent settlements scanned (its history is longer than the 2000-row scan cap).

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xec55e5…94aadb
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xf46261…b0d29c
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0x6664a1…0da626
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0x076713…154dfd
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xa980c0…f5bbae
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xd8311b…691c17
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0x33b8a9…4c8e32
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xa746e7…d7a811
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xd2bd1c…100510
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0x51fd98…a6d09c
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0x8a8708…33fda0
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xfc2e68…10c134
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xa58a69…33aab7
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xff13e5…9d32e2
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xbc9ca4…51323e
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0x5affe9…241de2
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xa9f9a4…c0b2fa
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xcde6be…231f47
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xba0b33…5d7e80
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xb2fa3f…6ddb60
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0x7a7cfc…397442
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0x6fd785…867755
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0x199161…72b936
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0xbaf175…8cc8d4
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa61d ago0x676bbb…7e24b8

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

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

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: 0xa49e…fe34

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