SNSYS puts finished AI solutions into the products you already run. Three ways in: a REST API, an npm package, and the dashboard. Voice is live today. One call reads a website, synthesizes what a receptionist needs to know, assigns a real number, and returns an agent that answers, takes messages, and sends texts and emails.
median from website to live receptionist
endpoints: one POST to deploy, one GET to poll
live in under a minute
Provision timings measured across 155 business deploys through the demo and onboarding funnel, March through June 2026.
The same deploy runs as an API call from a backend, as a tool call from an AI coding agent, or as a click in the dashboard. Each one returns the same working receptionist on the same number.
curl -X POST https://app.snsys.ai/api/v1/voice/deploy \ -H "Authorization: Bearer $SNSYS_API_KEY" \ -H "Content-Type: application/json" \ -d '{"business_name": "Cedar Lane HVAC", "website_url": "https://cedarlanehvac.example"}' # 202 Accepted, then poll until ready { "status": "ready", "phone_number": "+18605550136" }
Two endpoints: one POST to deploy, one GET to poll. Bearer auth, documented status and error states. The full contract is in the quickstart.
$ npx @snsys/voice deploy \ --key sk_live_... \ --site cedarlanehvac.example \ --name "Cedar Lane HVAC" Ready. +1 (860) 555-0136 answers for Cedar Lane HVAC. // same package, as an MCP server in Claude Code or Cursor: { "mcpServers": { "snsys-voice": { "command": "npx", "args": ["-y", "@snsys/voice"], "env": { "SNSYS_API_KEY": "sk_live_..." } } } }
@snsys/voice deploys from any terminal or CI, and doubles as a Model Context Protocol server so Claude Code or Cursor runs the deploy from one instruction. Get a key.
For anyone on the team who would rather click than call an API. The dashboard runs the same provisioning, on the same platform.
The knowledge is synthesized from the website before the agent answers. The prompt and the knowledge base arrive already written.
An API hands back numbers, call control, and transcription. The agent is still yours to design, prompt, wire, and maintain.
A dashboard walks one business through setup at a time, by hand. Fine for one client. Fifty clients means fifty afternoons.
One call returns a working receptionist built from the website: knowledge, number, answering real calls. Activation completes it. Repeat per client.
Every solution provisions the same way: isolated, metered, and tagged to the client. Voice leads with a documented deploy API and an npm package. The rest run in the dashboard today.
A receptionist built from a website, live on a real number from one call. Answers, messages, texts, emails.
Camera video analysis, threat detection, and alerting.
Enrichment and follow-up across the pipeline.
An AI render pipeline for short-form video.
Captive-portal sessions and on-network engagement.
Generated business sites, edited from chat.
Booking, calendars, and reminders.
Payment outreach by call and text.
Ad campaign creation and tuning.
Voice ships a documented deploy API and the @snsys/voice npm package today.
The agent's knowledge is synthesized from the website before it goes live: services, hours, FAQs, transfer rules, voice guidance, assembled for you before the first call.
Async 202 and poll, documented status and error states, two-node voice behind a health-checked load balancer, interruption handling, failover, and monitoring. The reliability work arrives done.
Every deploy is isolated and tagged to the requesting organization. A poll for another org's agent returns a 404. The agent answers under the client's own name, with no SNSYS mention to the caller.
One repeatable call provisions one client. Run it across the whole book the same afternoon, a live receptionist back each time, each one metered on its own.
Pick a client. Send their website. In about a minute a phone number answers for that business, and the client hears their own receptionist, live. Run it as a recurring line item across the book: one deploy per client, billed monthly. Design partner pricing is set on the call. Book it.
Keys and trial deploys are self-serve; activation is set up with the team. Here is the line between what runs from a call today and what gets turned on with you.
The bare deploy returns a trial agent that answers, messages, texts, and emails. Booking, live transfers, and a dedicated number turn on at activation, which the SNSYS team handles during the partner program.
A trial agent answers on a shared pool number. A persistent, client-owned number is assigned at activation.
Voice has the public deploy API and the npm package now. The rest of the catalog is configured in the dashboard, with broader API access opening as the program grows.
Sign up, verify your email, and generate a key in the dashboard — no payment details for trial deploys. Trial keys run 20 deploys an hour and 5 active trial agents per account. Get a key.
The agent answers as the client, with no SNSYS shown to the caller. A partner-branded portal and self-serve billing are on the roadmap.
Design partner terms are agreed directly, so the program fits the size of the client book.
Sign up, generate a key, and send a client URL. The receptionist answers about a minute later. Prefer a guided run? Book fifteen minutes and watch it go live on the call.
Keys are self-serve: sign up, verify your email, and generate one. Trial deploys need no payment details.