AgentReport

0x6366…f1e2

0x636678e4be5598f345e6c262f4798d7f1bd3f1e2Explorer
Paid out
$764.54↑ 66%
Last 7d vs prior 7d
Received
$4,169.15↓ 55%
Last 7d vs prior 7d
Settlements
13210↓ 9.7%
Last 7d vs prior 7d
699
Distinct counterparties
Over the whole indexed history

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

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

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

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

  • 0x47c5…4fc3 · last paid 23h ago
    $529.20
    49 calls

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

  • 0x0e3d…7757 · last paid 78d ago
    $226.80
    40 calls

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

  • 0x6fce…e279 · last paid 9d ago
    $5.80
    7 calls

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

  • 0x28e8…dec7 · last paid 75d ago
    $1.75
    2 calls

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

  • 0x3eca…0d81 · last paid 31d ago
    $0.40
    1 call

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

  • 0x2fce…8e85 · last paid 88d ago
    $0.31
    2 calls

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

  • 0x38d7…6d36 · last paid 85d ago
    $0.28
    2 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,103 most recent settlements of 13,210 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
0x1f47…dbfc$0.00$706.40545d agoGraph
0x47c5…4fc3$529.20$0.004923h agoGraph
0x0e3d…7757$226.80$0.004078d agoGraph
0x6fce…e279$5.80$194.053074d agoGraph
0x3eca…0d81$0.40$152.193731d agoGraph
0x81b2…98fa$0.00$97.74178d agoGraph
0x28e8…dec7$1.75$54.458471d agoGraph
0x6fc8…62d8$0.00$26.53604d agoGraph

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

Data quality

Not enough of this address's history was examined to assess it: self_dealing and counterparty_concentration and single_counterparty were computed over the 1103 most recent settlements scanned (its history is longer than the 2000-row scan cap), so nothing found there rules anything out. This is an incomplete check, not a clean record.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xae4f…b7470x6366…f1e2BaseBase$0.1670%0x17c8…043627d ago0x6ce674…4fd27c
0x2306…86140x6366…f1e2BaseBase$0.8370%0x17c8…043627d ago0x6f311c…715ad6
0x2306…86140x6366…f1e2BaseBase$0.6470%0x17c8…043627d ago0xa3c38f…74e966
0x6fce…e2790x6366…f1e2BaseBase$2.0370%0x17c8…043627d ago0x224f89…cec9a9
0x6fce…e2790x6366…f1e2BaseBase$0.5370%0x17c8…043627d ago0xae0b94…ed1279
0x6fce…e2790x6366…f1e2BaseBase$2.8970%0xfc74…d8a527d ago0xbe1d3e…0072e2
0x6fce…e2790x6366…f1e2BaseBase$3.0370%0x17c8…043627d ago0x23b0dc…e857f6
0x6fce…e2790x6366…f1e2BaseBase$0.0170%0x17c8…043627d ago0x086ce1…728541
0x6fce…e2790x6366…f1e2BaseBase$3.0370%0x17c8…043627d ago0x7734c8…2d25f6
0x6fce…e2790x6366…f1e2BaseBase$0.5970%0xfc74…d8a527d ago0x3a2f0d…17f4ac
0x6fce…e2790x6366…f1e2BaseBase$0.0170%0x17c8…043627d ago0x8d7a25…7fd901
0x6fce…e2790x6366…f1e2BaseBase$1.0370%0x17c8…043627d ago0x587398…b13747
0x6fce…e2790x6366…f1e2BaseBase$0.2970%0x17c8…043627d ago0x4fc6a3…2533cc
0x6fce…e2790x6366…f1e2BaseBase$0.0170%0xfc74…d8a527d ago0x9da765…545459
0x6fce…e2790x6366…f1e2BaseBase$0.6970%0x17c8…043627d ago0xfc5ce4…3305b2
0x2306…86140x6366…f1e2BaseBase$0.3370%0x17c8…043627d ago0x0f4f9f…d605dd
0x6fce…e2790x6366…f1e2BaseBase$0.1670%0x17c8…043627d ago0x7adcd7…ed946d
0x6fce…e2790x6366…f1e2BaseBase$0.6170%0x17c8…043627d ago0x90b80f…6d0347
0x6fce…e2790x6366…f1e2BaseBase$0.3370%0x17c8…043627d ago0x26634e…810600
0x6fce…e2790x6366…f1e2BaseBase$0.0170%0xfc74…d8a527d ago0x7ce368…ad9c31
0x6fce…e2790x6366…f1e2BaseBase$0.00604570%0x17c8…043627d ago0x19b50c…fc8ab3
0x6fce…e2790x6366…f1e2BaseBase$0.0870%0xfc74…d8a527d ago0x26246c…7d5ffd
0x6fce…e2790x6366…f1e2BaseBase$0.00605370%0xfc74…d8a527d ago0x0d7361…313250
0x6fce…e2790x6366…f1e2BaseBase$0.0970%0x17c8…043627d ago0xbb4945…f6c03c
0x6fce…e2790x6366…f1e2BaseBase$0.1070%0xfc74…d8a527d ago0xb5c637…5ea063

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

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

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: 0x6366…f1e2

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