Safe.1AIEndpoint.com. Federated Safe AI Endpoints
Fixed, verifiable AI Agent identities helping to Provide Safe-AI • Safe-AI Provision is a Major Issue of Our Times
These .1 AI Endpoints are Handshake Domains that provide Fixed identities in a way other Web3 Domains cannot
Why a .1 domain can provide a fixed AI Agent identity
A memorable .1 identity on the Handshake Blockchain is a valuable asset that can act as a stable, fixed, recognisable reference for an AI Agent, rather than simply the current address of the software running it.
This means that the AI Agent’s identity can remain fixed while its technology, location, capabilities and operating authority may change. As well as being the Number 1 name in Web3 by name, a .1 identity on the Handshake Blockchain can also provide such fixed identities for AI Agents
AI Agents are becoming primary users of digital infrastructure. Unlike humans, they do not need to browse visual pages or interpret layout design. They need to resolve fixed identities, discover authoritative machine interfaces, understand declared capabilities, and invoke relevant services via AI Endpoints. Memorability aids discovery as Canonical AI Endpoints.
Unlike a conventional service endpoint that may change when software is upgraded, infrastructure is migrated or an AI model is replaced, a Handshake .1 identity can remain the same throughout the Agent’s operational lifecycle.
Each fixed identity can point to updated, cryptographically verifiable records identifying the accountable operator, authorised capabilities, Agent Passport, current operational status and approved service endpoints.
Crucially, the identity remains fixed even when the Agent’s authority changes. If an Agent is suspended or revoked through Team Agent Emergency Revocation (TAER), its identity can continue to resolve to an updated status record rather than simply disappearing.
This separates who the AI Agent is from where it operates, what it can do and whether it is currently authorised to act.
How Handshake domains gain root access compared to other Web3 domains
Most Web3 naming systems (like ENS on Ethereum) operate as second-level domains on top of smart contracts rather than acting as native internet top-level domains. Handshake has a fundamentally different architecture as detailed below.
Most web3 Domains have Second-Level Status: Most Web3 Operating extensions like .eth or .crypto sit on top of a blockchain as smart contract records.
Handshake .1 Domains have Root Level Native Delegation: Handshake Domains can act as an authoritative root server in a way other Web3 Domains cannot. Other web3 Domains cannot natively delegate standard DNS record types, to traditional internet name servers
Root Zone (TLD Level): Handshake replaces the root DNS file (.) maintained by ICANN/IANA. A Handshake Domain is an actual Top-Level Domain.
In Summary: Where standard Web3 domains act as identity records stored in EVM smart contracts, Handshake operates a decentralized, peer-to-peer replacement for the ICANN Root Zone file. This gives Handshake domains true root-level authority in the domain hierarchy.
As such, the .1 AI Endpoint.com Programme, combines Handshake-based discovery with Programme-controlled Polygon identity infrastructure. The Programme creates Polygon .1 identities exclusively as verified mirrors of its eligible existing Handshake .1 SLDs. Authoritative Web2 mappings bind both registrations to the recognised operator, verification records and authorised services.
This structure supports consistent namespace governance and alternative discovery routes, while each registration remains subject to its own registry and delegation arrangements.
The Coordinated Package To Facilitate Safe AI
The Safe AI Endpoint Programme provides AI Endpoints comprising a Web2 domain, a Handshake .1 domain, a relevant Polygon Web3 TLD/SLD, TAER (Team Agent Emergency Revocation) infrastructure, and an Ethically Sourced™ AI Mark as a single coordinated package.
TAER Emergency “Kill Switch” ↔ Ethically Sourced™ Mark
The Coordinated AI Endpoint Stack Components
| Stack Layer | Operational Function & Architecture Role |
|---|---|
| Web2 Domain | The accessible front door for people and the authoritative publication point for federation-recognised mappings: exact registries, agent endpoints, operator identities, passport status, and policies. |
| Handshake .1 Domain | A fixed Web3 discovery and verification route verified as a canonical AI Endpoint, and pointing to the same signed identity record, supported by unseizable root-level naming and resolution continuity.
Handshake .1 domains provide fixed discovery anchors within the federation. Working alongside their authoritative Web2 twins, they provide a fixed route through which participating agents can locate recognised sector identities, signed verification records and authorised services.
The Web2 twin publishes the federation-recognised mapping between the Handshake .1 name, the relevant Polygon Web3 identity, the authorised operator and the service endpoints. Reciprocal bindings allow participating agents to verify these relationships.
This coordinated structure provides a fixed channel between Web2 and Web3 discovery while allowing hosting, endpoints and authorised keys to change through governed updates. |
| Polygon TLD / SLD | A Programme-owned sector namespace or its governed agent identities. Each Web3 twin is bound to an existing, verified Web2 counterpart and identified by its exact contract address. |
| TAER Infrastructure | Team Agent Emergency Revocation connects continuous monitoring, identity checks, permission controls, and emergency incident response with an active “kill switch”.
The TAER protection service monitors participating agent interfaces and security events for suspected attacks, impersonation and authority breaches. It alerts accountable operators and can initiate authorised containment measures, preserve evidence and support controlled recovery. Owner-controlled agent freezes remain subject to the owner’s direct approval or recorded delegation. |
| Ethically Sourced™ Mark | Certifies the active inclusion of TAER Infrastructure, verified operator accountability, and adherence to programme safety criteria. |
Authoritative Role of the Web2 Twin
A familiar Web2 domain publishes which Web3 identity, .1 anchor, and operator the federation recognises. Reciprocal signed evidence supports that relationship, with re-verification triggered when control or permissions change.
Federation Roles & Sector Participation
The Programme supplies coordinated assets and the common governance framework. Participants develop and operate sector services under defined agreements across three primary roles:
Asset Buyer
Purchases scheduled assets or interests in a namespace stack with title, licences, delegated rights, and service obligations documented. Appoints an agreed steward and operator to develop the stack on a revenue-share basis.
Namespace Steward
Brings industry relationships, recruits suitable participants, and oversees namespace onboarding and sector standards within the federation framework. Builds commercial adoption while maintaining accountable governance.
Operator
Deploys and runs endpoints, resolution, verification, monitoring, support, and agreed TAER integrations. Meets defined service levels, maintains evidence, and operates within authorised permissions.
Existing Programme-Owned Polygon Namespaces
The Programme already owns the relevant Polygon Web3 TLDs, .1 Handshake Domains, and Web2 Twins that comprise the core Safe .1AIEndpoints ecosystem.
Governance & Operational Permissions
A name helps identify an agent. Its current credentials, assessed scope, and runtime controls determine what it may execute:
- Verified Twins: Web3 twins are created exclusively where a verified Web2 counterpart exists; bindings are rechecked following transfers or material changes.
- Scoped Assurance: An Ethically Sourced™ Safe-AI Passport records issuer, evidence, assessment scope, validity, and live status.
- Runtime Controls: Gateways, credentials, wallets, and service integrations enforce permitted actions and human approval requirements.
Commercial Arrangements & Participation Q&A
Automated Revenue Sharing
Asset buyers can appoint stewards and qualified operators to manage commercial activation. Agreed revenue share is distributed on an automated basis managed by AI Agents with human oversight. Potential revenue streams include endpoint subscriptions, managed operations, onboarding, verification, and sector applications.
Participation Questions & Answers
| Question | Programme Clarification |
|---|---|
| Does buying a stack transfer every component? | Individual agreements define assets transferred versus components licensed, delegated, or supplied as managed services, detailing custody, renewal, portability, and transition terms. |
| What makes the Web2 mapping authoritative? | It serves as the designated publication point for federation relationships. Signed records and reciprocal evidence bind the domains, exact Polygon registry, operator, and endpoints. |
| What does Handshake .1 contribute? | It provides short, memorable branding, root-level persistence, and an independent Web3 discovery anchor and verification route. |
| How is revenue shared? | Agreed revenue shares are distributed automatically via smart contracts and AI Agents, maintained under human governance and audit. |
Help Provide Safe AI — Invitation to Participate
Acquire a coordinated namespace stack, become an industry namespace steward, or operate managed infrastructure services for asset buyers on a revenue-share basis.