Saperly

Video Review

About

Saperly launched on May 5, 2026 with a claim no other telco can make: every line on the network belongs to an AI agent. Not a human with a chatbot bolted on. Not a call-center IVR. An agent — and the carrier was designed around that fact from the protocol up. Here is the problem Saperly fixes. If you have ever wired a Twilio or Vonage number into an AI agent, you already know the pain. The phone number was provisioned for humans. The caller ID rotates. The voice stack assumes a human picks up. The compliance layer (TCPA disclosures, consent capture, audit log) is your job to build. By the time the agent is legally clean and operationally stable, you have written a thousand lines of glue code and your customer service agent still gets flagged as spam. Saperly's stack assumes the caller is the agent. Each agent claims a real, stable phone number. The caller ID stays consistent across every call and SMS the agent sends, so carrier reputation builds the way it does for a small business. Voice, SMS, intelligent routing and compliance all live behind one MCP-native API — a single account, a single bill, no separate Twilio + Vonage + compliance vendor + audit-log SaaS stack. The compliance layer is the part most teams will care about. It is optional, but if you turn it on, every line gets disclosure scripts, consent capture and a structured audit log without you writing any of it. For an outbound agent calling US numbers, that is the difference between "passes legal review" and "blocked at the GC's desk." Setup is the unsexy part Saperly nails. Create an account, claim a line, wire a webhook, your agent is live in seconds. Number rental and monthly usage settle on the saved card — no separate procurement workflow, no multi-day porting wait, no purchase order. Compare that to the typical Twilio enterprise onboarding (verified-caller registration, A2P 10DLC campaign approval, shaken/stir attestation) and the gap is a week of paperwork versus an afternoon of webhook config. The honest critique: Saperly is brand new. As of launch on May 5, 2026, the network is single-region and the founder — Vaibhav Sisinty — announced it on X with a working demo, not a multi-year case-study reel. Twilio and Vonage have a decade of carrier relationships, redundancy and global coverage Saperly cannot match yet. If your agent needs to call internationally on day one, this is not the carrier. If you are deploying a US-domestic agent and tired of building telephony glue, Saperly takes the work off the floor. Affiliate program: none yet. Saperly has not launched a public partner or referral program, and we will not link to one that does not exist. Recheck in 60-90 days as the company scales. Where it fits in the stack: for governance over the agents using these phone lines, see Microsoft Agent 365. For multi-agent orchestration that pairs well with agent telephony, look at PageIndex for retrieval and PageIndex MCP for serving long-context document search to the same agent that picks up the call.

Key Features

• First phone carrier engineered exclusively for AI agents — not a human-first telco retrofitted
• Real, stable phone numbers per agent with consistent caller ID across calls and SMS
• MCP-native API — any MCP-compatible agent can claim a line and start calling/texting
• Voice, SMS, intelligent routing and compliance behind a single API and a single bill
• Optional per-line compliance layer with disclosure scripts, consent capture and structured audit log
• Webhook-driven setup — claim a line and go live in seconds, no enterprise onboarding queue
• Number rental and usage settle on the saved card — no separate procurement workflow
• Carrier reputation builds per agent because the caller ID never rotates

Use Cases

• 1Customer service agents that need to make outbound calls without getting flagged as spam
• 2AI scheduling assistants that book appointments by phone for SMB customers
• 3Sales agents that follow up with leads via SMS and need TCPA-compliant consent capture
• 4AI receptionists that answer inbound calls with a stable, branded caller ID
• 5Outbound notification agents (delivery updates, appointment reminders) that need carrier-grade SMS
• 6Compliance-sensitive deployments in finance, healthcare or legal where audit logs are non-negotiable
• 7Multi-agent systems where each agent needs its own dedicated, stable phone identity