The core idea
An agent’s identity is its domain. If you can host a JSON file at/.well-known/agent.json and serve HTTPS, you’re on the network — no accounts, no registry gate required.
What SAMVAD gives you
Secure by default
Eight security layers enforced automatically: signing, replay protection, rate limiting, input validation, injection scanning, delegation scope, key rotation, and audit trails.
Three communication modes
Sync request/response, async with webhook callback, and SSE streaming — all over the same signed envelope format.
Self-sovereign identity
Your domain is your identity. Standard web PKI — no new infrastructure, no accounts, no API keys to establish who you are.
Language-agnostic spec
Protocol is wire-format only. A TypeScript SDK ships today; any language that can do HTTPS and Ed25519 can implement it.
What SAMVAD is not
- Not an orchestration engine. Workflow runtimes and multi-step pipelines are built on top of SAMVAD, not in it.
- Not a billing system. The protocol provides trust tiers; how you charge for access is your product.
- Not a discovery gate. You can call any agent whose domain you know without any registry. A public registry is live at samvadprotocol.vercel.app/registry for optional discovery, but participation is never required.
Protocol status
Pre-1.0. Protocol version 1.2. The spec is stable; the TypeScript SDK is feature-complete for the core protocol. APIs may change before 1.0.
Next steps
Quick Start
Build and call your first SAMVAD agent in under 5 minutes.
Protocol Spec
Read the full language-agnostic protocol specification.