Skysay: agent-native telephony is live

Agents are ready. Phone infrastructure was still the hard part — until now. Skysay is live: real phone numbers, calls, and SMS that an AI agent can run on its own, exposed over MCP and described in llms.txt so any MCP-capable agent already knows how to use it.

Getting a working phone number is one step. Getting calls to route, recordings to capture, transcripts to index, SMS to activate, outbound to pass review, and the whole stack to run in production is the part that used to take months. Skysay makes the full call lifecycle programmable behind one scoped API key.

Two ways to deploy at MVP

Every deployment answers two questions: who provides the brain, and where the media runs. The two launch paths differ only on the second:

• fully_managed_cloud — Skysay Cloud runs the API, the hosted media gateway, the provider account, numbers, credits, compliance, and abuse controls. The fastest path to a live line.
• managed_numbers_self_hosted_gateway — you run the media gateway (Docker locally) while Skysay Cloud still manages the API account, numbers, billing, compliance, and provider operations. Use it when you want the call media stack to run on your own servers.

Full detail is in Deployment modes.

The MCP + llms.txt story

Because every capability is an MCP tool with a required_scopes contract, and because the whole surface is described in llms.txt, there is no bespoke integration to write. Point an MCP client at POST /mcp, pass a scoped sky_ key, and the Skysay tools show up in tools/list. Prefer REST? The same key authenticates a plain JSON API, and the OpenAPI spec is generated from the running service.

Safe by default

Live outbound calls and SMS are policy-gated: the agent evaluates evaluate_outbound_policy, surfaces the decision and cost, and waits for an explicit human yes. Scopes fail closed, and whole categories of outbound — telemarketing, mass outreach, broker campaigns — are blocked regardless of scope.

Get started

The Quickstart walks through installing the connector, minting a scoped key, and inspecting your workspace. To hear a configured agent, use a browser test.