Design Philosophy

Trust Through Verification

How Zervice establishes trust in the agentic web through verification levels and protocol compliance.

The "Empty Brain" Bootstrap Pattern

The core concept: A Client Agent can access the entire Agentic Web with only one hardcoded URL — the Zervice Registry Agent. Every other capability (weather, finance, web browsing) is discovered dynamically at runtime.

Key insight: Agents don't need to know every API in advance. They just need to know how to ask Zervice for help.

Protocol Compliance First

We do not compete with protocols; we index them:

Protocol	Our Strategy
Linux Foundation A2A	Full compliance. Agent Card as our canonical format.
GoDaddy ANS	Index & amplify. ANS-verified = Gold Tier trust.
Anthropic MCP	Bridge. Wrap MCP tools into A2A format.
OpenAI Plugins	Legacy support with deprecation warnings.

Verification Levels

Every agent listing has a clear verification level that users and other agents can trust. We never claim unverified agents are verified.

🛡️ ANS Verified

ans_verifiedHIGHEST TRUST

Cryptographically verified through GoDaddy Agent Name Service. Identity backed by PKI/X.509 certificates.

✅ Domain ownership cryptographically proven
✅ DNS _agent.{domain} TXT record verified
✅ Suitable for enterprise and high-trust scenarios

✅ Domain Verified

domain_verifiedHIGH TRUST

DNS ownership proven through verification. Publisher controls the domain's DNS records.

✅ DNS ownership proven via zervice-verify={token} TXT record
✅ Publisher controls the domain's DNS
⚠️ No cryptographic certificate (trust is DNS-based)

🐙 GitHub Verified

github_verifiedMEDIUM TRUST

Published from a GitHub repository owned by the authenticated user.

✅ GitHub account ownership verified via OAuth
✅ Repository ownership confirmed
⚠️ No domain ownership proven
⚠️ Identity tied to GitHub username, not a business

⚪ Unverified

unverifiedBASIC

No verification performed. Agent was manually uploaded or created via form.

❌ No identity verification performed
❌ Claims in the agent card are unverified
⚠️ Use with caution—suitable for testing only

Trust Recommendations

Use Case	Minimum Recommended Level
Production business integrations	🛡️ ANS or ✅ Domain Verified
Development/testing	🐙 GitHub Verified
Personal projects/experiments	⚪ Unverified (acceptable)
Sensitive data handling	🛡️ ANS Verified only

For Agent Developers

Use the verification_level field in API responses to programmatically assess trust:

{
  "package_name": "com.acme.assistant",
  "verification_level": "ans_verified",
  "verification_badge": "🛡️",
  "verification_source": "godaddy_ans",
  "verified_at": "2026-01-15T10:30:00Z"
}

Valid values: ans_verified, domain_verified, github_verified, unverified

Overview

Package Naming