Developers · 5 of 7
Agent identity standards
ENSIP-25, ENSIP-26, ERC-8004, ERC-8217, and verification grades.
betaserver 3.0 · 79 MCP tools · platform contract v1Verified 2026-07-29Owner: ENS.Tools Developer Platform
ENS.Tools implements draft standards conservatively. Published records, registry entries, custody, endpoint health, and reputation remain separate evidence rather than being collapsed into one “verified” badge.
ENSIP-26: agent-context and agent-endpoint[mcp|a2a|web].
ENSIP-25: agent-registration keys using an ERC-7930 interoperable registry address and agentId.
ERC-8004: identity registration files, mint/update preparation, and reviewer-scoped reputation.
ERC-8217: agent NFT binding inspection.
ERC-8183: draft job escrow preparation and strict funded-evidence checks.
Production contract
Before you run this workflow
Networks
- Ethereum mainnet for onchain plans
- HTTPS for MCP and public APIs
Prerequisites
- JSON-RPC 2.0 client for MCP
- Read the live platform contract and tool schemas at runtime
Wallet permissions
- MCP never receives private keys
- Prepared writes must be reviewed, signed, and broadcast by a separate wallet
Expected result
- Structured JSON data or an unsigned plan with chain, target, calldata, value, and safety metadata
Errors and recovery
- Call tools/list again after schema errors
- Back off after rate limits
- Simulate immediately before signing
ENSIP-25 verification grades
bidirectional — the registry file and ENS record agree and control matches
registered-custodial — registry and ENS agree but a third party holds the identity
self-asserted — a claim exists but registry-side proof is incomplete or unreadable
mismatch — the registry entry points to a different ENS identity
none — no supported claim is present
Evidence this does not create
Software safety
Truth of advertised capabilities
Future endpoint availability
Permission to transact
Unscoped reputation or economic guarantee