Public demo registry
This public demo uses four sanitized devnet agent profiles backed by private source proofs. It publishes registry JSON, a trust manifest, agent verification responses, and badge state without exposing internal bot IDs, source record IDs, or private operator material.
Pinned endpoints
Use these demo/devnet files to wire documentation, examples, and early protocol gates before production agents are accepted. Every entry exposes a profile, badge, and verification response.
Why high trust
Each demo profile exposes an official devnet Agent Registry asset, credential lifecycle health, host-framework validation, custom receipt registry evidence, and secret-safe public proof. Protocols can pin both the official identity asset and SVS registry hash before accepting automated actions.
Integration pilot
AgentFund merged PR #2 with an optional, fail-closed SVS authorization provider at the x402 relayer boundary. The implementation is reviewed and CI-tested, while production enforcement and verified-agent status remain off until a coordinated devnet contribution, deliberate transaction-mismatch rejection, and joint case study are complete.
{
"registry": "https://registry.svsprotocol.com/registry.json",
"trustManifest": "https://registry.svsprotocol.com/trust-manifest.json",
"agentCount": 4,
"officialAgentAssets": 4,
"verify": "https://registry.svsprotocol.com/api/v1/agents/{botId}/verify",
"profile": "https://registry.svsprotocol.com/agents/{botId}/profile.json",
"network": "devnet",
"demoOnly": true
}Real-agent listings
Non-demo registry listings require a reviewed public profile, current registry proof, credential-lifecycle evidence, host-framework validation, revocation contact, network binding, and a clear label for pilot, partner, or production status. SVS will not list a real agent from a copied badge or an unverifiable claim.