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.84M Roundhouse has indexed across 1,397,496 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%fluxa66d ago0xebf73c…52a7d5
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x231f31…98a531
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0xf3a4af…2d32bf
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x72c3da…9ce5f7
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0xf54117…e88fa8
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x083b5b…968393
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x7fced8…7ca06f
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0xcdcbd0…fcf7da
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x05e298…1ab419
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x9c6365…39f618
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x487b28…38c08f
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x25ff92…6e5c16
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0xe83fcc…8ad479
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0xc8f493…b019cf
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0xd63294…a7015b
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0xc74e21…24c598
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0xc4b617…efef48
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x0c7601…d1adfa
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x64924d…1dce7c
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0xbbc5b7…42851a
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x5ef64b…aec9fe
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0xdfe0ed…0d71ff
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x6bf78f…7ad9a3
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x9a84fb…6e0dfc
0xa49e…fe340xfe80…47eeBaseBase$0.001100%fluxa66d ago0x9b61ca…992c20

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.