AgentReport

0x44ba…d357

0x44ba1debc6ea2aef1ef76aa5d968e8102a2ed357Explorer
Paid out
$0.73
Last 7d vs prior 7d
Received
$0.54
Last 7d vs prior 7d
Settlements
67
Last 7d vs prior 7d
3
Distinct counterparties
Over the whole indexed history

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

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

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

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

  • 0x3577…ca8d · last paid 36d ago
    $0.73
    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

MayJunJulAugSepOctNov
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x3577…ca8d$0.73$0.00136d agoGraph
0x0bf5…0155$0.00$0.5364361d agoGraph
0xfd44…431c$0.00$0.0016022368d agoGraph

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

Data quality

58% of observed volume is with a single counterparty, in all 67 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x44ba…d3570x3577…ca8dBaseBase$0.7370%0x642b…6c7536d ago0x41d460…f17872
0x0bf5…01550x44ba…d357BaseBase$0.02100%questflow361d ago0xd9fd18…6e21b2
0x0bf5…01550x44ba…d357BaseBase$0.005683100%questflow361d ago0x5138e8…70ade0
0x0bf5…01550x44ba…d357BaseBase$0.008536100%questflow361d ago0x3c7fba…1c48fe
0x0bf5…01550x44ba…d357BaseBase$0.002372100%questflow361d ago0x0ce3d8…6627f4
0x0bf5…01550x44ba…d357BaseBase$0.007211100%questflow361d ago0x95a88c…2bcb4d
0x0bf5…01550x44ba…d357BaseBase$0.009951100%questflow361d ago0xc6fd29…50b5f4
0x0bf5…01550x44ba…d357BaseBase$0.03100%questflow361d ago0x847240…984269
0x0bf5…01550x44ba…d357BaseBase$0.02100%questflow361d ago0xcb5da5…9a290d
0x0bf5…01550x44ba…d357BaseBase$0.01100%questflow361d ago0xe10633…9c02c3
0x0bf5…01550x44ba…d357BaseBase$0.02100%questflow361d ago0xd8a5ee…10a555
0x0bf5…01550x44ba…d357BaseBase$0.003242100%questflow361d ago0xbe0e7f…fd3c6c
0x0bf5…01550x44ba…d357BaseBase$0.01100%questflow361d ago0xd31beb…14a42a
0x0bf5…01550x44ba…d357BaseBase$0.004157100%questflow361d ago0xa3c07d…fb86fa
0x0bf5…01550x44ba…d357BaseBase$0.02100%questflow361d ago0xb4c000…e335d2
0x0bf5…01550x44ba…d357BaseBase$0.002765100%questflow361d ago0xd6ed76…1e31b6
0x0bf5…01550x44ba…d357BaseBase$0.02100%questflow361d ago0xee68d4…f56c13
0x0bf5…01550x44ba…d357BaseBase$0.03100%questflow361d ago0x4ad07c…5dee8a
0x0bf5…01550x44ba…d357BaseBase$0.003895100%questflow361d ago0x2c0ac7…084a5a
0x0bf5…01550x44ba…d357BaseBase$0.007624100%questflow361d ago0xcffdbb…9ebd6e
0x0bf5…01550x44ba…d357BaseBase$0.01100%questflow361d ago0x4bc92c…078ed0
0x0bf5…01550x44ba…d357BaseBase$0.02100%questflow361d ago0x0eef6b…b4e8b5
0x0bf5…01550x44ba…d357BaseBase$0.04100%questflow361d ago0x8059f9…6a09f9
0x0bf5…01550x44ba…d357BaseBase$0.03100%questflow361d ago0x3e21c7…8df5cf
0x0bf5…01550x44ba…d357BaseBase$0.01100%questflow361d ago0x50e451…9c98c7

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

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

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: 0x44ba…d357

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