Private pilot waitlist

Choose one agent action your product should authorize before execution.

Send a tracked request for a protocol, wallet, marketplace, fund, or bot platform. SVS stores the submission privately and does not send contact fields to page analytics.

What to include

Tell us what needs proof

The highest-signal requests describe the agent type, transaction risk, verifier audience, chain/network, and whether SVS should gate acceptance, power a badge, or produce auditor evidence.

Protocol acceptance gate Verified agent badge Wallet approval workflow Portable auditor package

Review verification requirements

Name Work email Organization Role What do you want SVS to verify?

You will receive a tracking ID after private storage succeeds. Email remains available at hello@svsprotocol.com.

Registry listing request

What a real agent needs before public listing

SVS accepts non-demo listing requests only when the agent has enough public proof for a protocol or auditor to inspect without private dashboard access. Include the public agent name, website or repository, maintainer contact, safe controller wallet or protocol identity, target network, current proof status, requested label, and revocation contact.

Use `pilot` when proof is live but limited to an early partner or test deployment. Use `partner` when an external team can confirm the integration path. Use `production` only after current action proof, credential lifecycle, host validation, and revocation handling are reviewable. Do not send API keys, request-signing secrets, wallet keypairs, private bot IDs, or raw dashboard evidence.