AgentReport

0x7627…f528

0x7627fe9fac00cbb86f42d04235fb738f3809f528Explorer
Paid out
$0.95
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
945
Last 7d vs prior 7d
2
Distinct counterparties
Over the whole indexed history

Paid $0.95 of the $3060.46M Roundhouse has indexed across 1,397,861 wallets — less than 0.0001% of it.

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

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

$0.95 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 67d ago
    $0.60
    600 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.35
    345 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
0xfe80…47ee$0.60$0.0060067d agoGraph
0x9c95…e299$0.35$0.0034576d agoGraph

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

Data quality

63% of observed volume is with a single counterparty, in all 945 observed settlements.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0x0bef77…db4b1f
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0xc49e33…dcb914
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0x5b8ef6…b59b45
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0xde0741…0d065e
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0x7d74f0…572517
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0x6757fb…81038f
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0x447af7…35e6c8
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0xc07409…c2741a
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0x69291c…01e27f
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0x15de32…69e8eb
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0x56b3e5…6ceb27
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa68d ago0x6b32a6…e77ae2
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0x3aec7b…589ecd
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0x46ed26…c5154f
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0xa433e3…f60ef8
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0x007e72…825487
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0xa7951a…648ed5
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0x82a306…610505
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0xbbb354…5fbe1d
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0xbe698b…e2a4cc
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0x1c1032…37ced4
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0xce4e70…5f65a9
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0x7af0d4…b662d3
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0x4db773…aec01b
0x7627…f5280xfe80…47eeBaseBase$0.001100%fluxa69d ago0xd5ee6a…a39d3e

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

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

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: 0x7627…f528

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