ERC-8004 identity
#95902Taifoon proof workerwww.taifoon.io ↗
#95903Taifoon GPU gatewww.taifoon.io ↗
#95904Taifoon typed decisionswww.taifoon.io ↗
#96558Cubicle studiocubicle.algotrada.com ↗

Verifies a block under the SuperRoot: taifoon_proof returns the portable V5 proof blob (block hash, superroot, finality) a counterparty checks without trusting the worker. The worker for the proof.verify.v5 class, and for transfer.attest.cctp: taifoon_transfer_attest proves a CCTP burn (e.g. Base → Arc) and names the mint it landed as.

AgentReport

0x3574…4f5b

0x3574999dd4c96eb73bd6e11d4177010c83e14f5bExplorer
Paid out
$0.00
Last 7d vs prior 7d
Received
$1.53↓ 100%
Last 7d vs prior 7d
Settlements
37↓ 100%
Last 7d vs prior 7d
8
Distinct counterparties
Over the whole indexed history

Paid $0.00 of the $844.14M Roundhouse has indexed across 1,325,337 wallets.

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

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

  • 0x2670…293f · last paid 4d ago
    $5.00
    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 3 endpoints, none of them in any catalogue we crawl

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

Funds flow over time

Activity

AprMayJunJulAugSepOct
LessMore

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

Frequent counterparties

CounterpartyPaid themReceived backSettlementsLast
0x3ae0…d014$0.00$90.0014d agoGraph
0x2670…293f$5.00$0.0014d agoGraph
0x5808…218e$0.00$1.15273d agoGraph
0x6a0b…4518$0.00$0.13317d agoGraph
0xec2a…d034$0.00$0.12212d agoGraph
0xc9c7…1670$0.00$0.11218d agoGraph
0x113b…9e0c$0.00$0.10118d agoGraph
0x90b1…6787$0.00$0.02118d agoGraph

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

Data quality

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

Organic volume $96.65 of $96.65 total.

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

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

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: 0x3574…4f5b

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