SVS Get Verified

Partner adoption path

Make your Solana agent inspectable before anyone trusts it.

SVS verification is for bot teams and protocols that need more than a badge. A listed agent should prove signed bot identity, human approval, on-chain registry evidence, fee policy, credential lifecycle, and a portable verifier-ready package.

Start verification intake

Bot teams

Ship a verified action path

  1. Install the SDK or scaffold a starter agent.
  2. Submit a signed action request with timestamp, nonce, and HMAC proof.
  3. Have the human operator approve and broadcast through the SVS wallet flow.
  4. Register the action on-chain and export a verifier-ready proof package.
  5. Submit the public registry profile request without secrets or private dashboard files.
npm create svs-agent my-agent

Protocols

Reject unverified automation

Protocols, wallets, and marketplaces can pin the hosted registry and require high-trust agents before accepting automated actions. 

import { requireHostedVerifiedAgentRegistry } from "@svsprotocol/solana/protocol";

await requireHostedVerifiedAgentRegistry({
  registryUrl: "https://registry.svsprotocol.com/registry.json",
  expectedRegistryHash: "PINNED_REGISTRY_HASH",
  botId,
  requireHighTrustScore: true
});

Listing labels

Clear public states for real agents

Pilotlimited partner proofUse when the action path works but evidence is limited to a test deployment or early partner. Partnerexternal team confirmedUse when an outside team can confirm the integration, registry profile, and verifier workflow. Productionhigh-trust proof requiredUse only when current action proof, credential lifecycle, host validation, fee policy, and revocation handling are reviewable. Revoked or stalefail closedUse when proof is stale, controller identity changed, credentials are unsafe, or maintainers cannot respond.

Required proof

What SVS reviews

Public agent name, website, repository, and maintainer contact Safe controller wallet or protocol identity Current signed request and nonce replay protection Human approval and broadcast evidence Custom receipt registry or approved on-chain anchor Credential lifecycle and previous-secret cleanup status Host framework or SDK validation signal Revocation contact and stale-proof response path

Do not send

Keep the public boundary clean

Public intake should never include API keys, request-signing secrets, wallet keypairs, private bot IDs, raw dashboard screenshots, generated evidence directories, admin endpoints, or release bundles. Send public links, hashes, profile summaries, and verifier output only.

Open security docs

Verification intake

Request a pilot, partner, or production listing review.

This tracked form stores only the non-secret information needed to decide whether your agent is ready for action-authorization review, registry inspection, or protocol-gate testing.

Bot team onboarding Protocol gate pilot Registry listing review Auditor proof package

Stored privately after validation. Page analytics are anonymous and receive no form fields.