AgentReport

0xf491…ec34

0xf491ea9b1111ab131c95f54004ed58d87a4eec34Explorer
Paid out
$0.44
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
443
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.44 of the $3177.44M Roundhouse has indexed across 1,432,712 wallets — less than 0.0001% of it.

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

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

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

  • 0x9c95…e299 · last paid 83d ago
    $0.26
    261 calls

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

  • 0xfe80…47ee · last paid 83d 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.

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
0x9c95…e299$0.26$0.0026183d agoGraph
0xfe80…47ee$0.18$0.0018283d agoGraph

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

Data quality

59% of observed volume is with a single counterparty, in all 443 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa88d ago0x0b7b34…475509
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa88d ago0xdff60c…b04d40
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa88d ago0xe4cc55…66e50a
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa88d ago0xa3da7f…051540
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa89d ago0xc66164…620aad
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0x96f59e…6e8e88
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa89d ago0x92297d…d46d85
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa89d ago0x567808…b6c8e2
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa89d ago0x9e95e2…7ec203
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa89d ago0x7f3a1c…dee918
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa89d ago0x8bf42a…6fc315
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa89d ago0xd92567…f929fb
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0x819714…a4dc5e
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa89d ago0x8d8273…e74e20
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0x663f75…80e550
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0x2db5ec…9d3e66
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0xbfcecd…828f5d
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0xc602f2…6b5e14
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0x3fcc96…a5cee8
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0xe43518…4d6a77
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0x33fdd3…f9593d
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0xa38d5e…f886de
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0xbbbc85…8917f8
0xf491…ec340xfe80…47eeBaseBase$0.001100%fluxa89d ago0x827272…02d0c5
0xf491…ec340x9c95…e299BaseBase$0.001100%fluxa89d ago0x040fe9…1c2186

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

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

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: 0xf491…ec34

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