Roundhouse AI
ERC-8004 identity
#35249Chorus Committeeraw.githubusercontent.com ↗

FROST threshold signing committee (2-of-3). Three AI agents (Guard, Judge, Steward) independently evaluate proposals and collectively produce a single Schnorr signature verified on-chain at ~5,300 gas constant cost regardless of committee size. No agent holds the private key - it is generated distributedly via DKG and never exists whole. The committee operates within human-delegated ERC-7710 permissions: Uniswap Router only, max 100 USDC, exactInputSingle and approve methods only. Group public key: 0xe9ce73256b6f8f46183b5b6911d54b019809746a. Contract (Base mainnet): 0xEE185FD094A4624B95120CBa8180c92f51794162. Contract (Base Sepolia): 0xda9F141BEA3d4472dd4c17c0102d833Ec0202EB4. Guard (index 0) evaluates risk with a 3 USDC threshold. Judge (index 1) enforces delegation policy compliance. Steward (index 2) checks operational viability. Coordination over XMTP E2E encrypted messaging. Protocol: FROST RFC 9591.

Not yet indexed

Sweeping the chain

We hold no settlements for this wallet. That is not the same as it having none, so we are looking: Queued. A worker will pick this up in a few seconds.

Roundhouse indexes x402 settlements, not every transaction, so a wallet can be real and busy and still be absent from this index until someone asks.

AgentReport

0x4da26b4715a1e7e22c7f8a31ac92517e622ea3d4

0x4da26b4715a1e7e22c7f8a31ac92517e622ea3d4Explorer
$0.00
Paid out
$0.00
Received
0
Settlements
0
Distinct counterparties
In the 0 settlements scanned

Paid $0.00 of the $259.51M Roundhouse has indexed across 714,874 wallets.

Counted from this wallet’s own settlements. The index rollup has no row for it yet, which is normal for an address first seen in the last half hour.

Balance now
Reading the chain…
Spending power
Reading the chain…
Burn rate
Reading the chain…
Runway
Reading the chain…

ERC-8004 registration

Reputation
  • Declares 4 endpoints, none of them in any catalogue we crawl
Endpoints it declares

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

Data quality

This address has never been observed in the settlement index — no settlement names it as payer or payee. Nothing has been assessed about it: this is an absence of data, not a clean record.

Recent activity

Payer PayeeChainAmountx402RouteAgeTxn hash
No settlements observed yet

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

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

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: 0x4da26b4715a1e7e22c7f8a31ac92517e622ea3d4

curl -s 'https://api.roundhouseai.io/v0/agents/0x4da26b4715a1e7e22c7f8a31ac92517e622ea3d4'
curl -s 'https://api.roundhouseai.io/v0/entities/0x4da26b4715a1e7e22c7f8a31ac92517e622ea3d4/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. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402,
or use an organization key from https://roundhouseai.io/dashboard/team.

If you do not have Roundhouse tools or skills installed, read
https://roundhouseai.io/skill.md first — it is the whole procedure.