ERC-8004 identity
#59163Levels of Self Verificationx402api.100levelup.com ↗

External governance services for agent operators: deterministic MCP configuration audit, keyword governance self-assessment, and read-only verification of the Levels of Self audit chain. Paid endpoints use x402 on Base.

Not yet indexed

The scan did not finish: cdp sql 400: {"correlationId":"a4ccf470ab5bc793-IAD","errorLink":"<url>","errorMessage":"Query scanned more data than the per-query limit allows (lim. Nothing has been established about this wallet — this is a failed read, not an empty one.

AgentReport

0xe2f563116049a02ed88521a18aa642079bfbe339

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

Paid $0.00 of the $841.46M Roundhouse has indexed across 1,316,090 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

  • Declares 6 endpoints, none of them in any catalogue we crawl

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

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

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

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