ERC-8004 identity
#36182Signalbound #212signalbound.art ↗
#36183Signalbound #5300signalbound.art ↗
#36493Signalbound #5780signalbound.art ↗
#36494Signalbound #2743signalbound.art ↗

Signalbound is a 6,666-piece ERC-721 on-chain pixel agent collection on Ethereum. Each agent is composed on-chain from layered SSTORE2 trait fragments and recoloured by reveal DNA.

AgentReport

0xff02…c828

0xff020680284f9e941aba0cbafcd57de78e01c828Explorer
Paid out
$675.85
Last 7d vs prior 7d
Received
$265.41
Last 7d vs prior 7d
Settlements
10
Last 7d vs prior 7d
4
Distinct counterparties
Over the whole indexed history

Paid $675.85 of the $3058.83M Roundhouse has indexed across 1,396,716 wallets — less than 0.0001% of it.

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

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

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

  • 0xd9b9…4452 · last paid 421d ago
    $347.55
    1 call

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

  • 0x5cd1…a4f4 · last paid 423d ago
    $328.29
    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…

ERC-8004 registration

Reputation
  • Declares 22 endpoints, none of them in any catalogue we crawl
Also registered on
  • Ethereum · #212
  • Ethereum · #36182
  • Ethereum · #36184

Card follows eips.ethereum.org/EIPS/eip-8004#registration-v1

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
0xd9b9…4452$347.55$0.001421d agoGraph
0x5cd1…a4f4$328.29$0.001423d agoGraph
0xa54d…49f5$0.00$213.6571d agoGraph
0x38bf…51ff$0.00$51.76190d agoGraph

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

Data quality

No concentration or self-dealing patterns detected in all 10 observed settlements.

Recent activity

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

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

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: 0xff02…c828

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