AgentReport

0xc974…86eb

0xc974ce5d962e766b071cc0ad45dff821b5db86ebExplorer
Paid out
$0.03
Last 7d vs prior 7d
Received
$0.00
Last 7d vs prior 7d
Settlements
260
Last 7d vs prior 7d
1
Distinct counterparties
Over the whole indexed history

Paid $0.03 of the $3067.43M Roundhouse has indexed across 1,401,575 wallets — less than 0.0001% of it.

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

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

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

  • 0x6482…b779 · last paid 276d ago
    $0.03
    260 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
0x6482…b779$0.03$0.00260276d agoGraph

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

Data quality

100% of observed volume is with a single counterparty; all observed volume is with one counterparty, in all 260 observed settlements.

Organic volume $0.03 of $0.03 total.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams323d ago0xaa1adb…ae55d0
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams323d ago0xf8f338…543f0b
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams323d ago0xc31096…0f04be
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams324d ago0xe4e75d…fd51c5
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams324d ago0x7aca7b…59d2fe
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams324d ago0xb996ae…ed070e
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams324d ago0xabbb1d…d747c7
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams324d ago0xccf0d0…ad29ac
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams324d ago0x2191a5…bd7d1f
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams324d ago0x407871…876cd2
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams324d ago0xdbb81d…81180d
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams324d ago0x430d0c…610fa5
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams324d ago0x657af7…8adf54
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x33bcbd…a4ecc7
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x184ee1…804ab6
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams325d ago0xaba757…2c3cee
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x53527a…d3f2d0
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams325d ago0xf98cfb…47be37
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams325d ago0xa6de7b…2e3254
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x205cc5…6abb98
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams325d ago0xda1408…ef8561
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x01d99c…935588
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams325d ago0x1dc284…199e4e
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams326d ago0x91812d…e70c09
0xc974…86eb0x6482…b779BaseBase$0.0001100%daydreams326d ago0x77e78b…1b3e05

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

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

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: 0xc974…86eb

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