Phone calls your software and AI assistants can make

SAGOT is built so that people and AI assistants can do the same things. Everything you can do on the website—create an agent, test it, publish it, add a phone line, import contacts, start a call and review what happened—is also an operation you can call from code.

One operation, three ways to call it

Every operation has a stable name such as agents.create, calls.create or calls.get. The same name, the same input and the same rules apply everywhere:

Surface	How you use it
HTTP API	POST https://sagots.com/v1/operations/<operation> with JSON and a bearer token. The full contract is published as OpenAPI at https://sagots.com/openapi.json.
MCP server	Connect your AI assistant to https://sagots.com/mcp (Streamable HTTP, bearer authorization). Each operation is a tool; dots become underscores, so calls.create is calls_create.
CLI	sagot operations lists what you can do, and sagot <operation> --input <file.json> runs one. Credentials are stored in a private file, never on the command line. The CLI is available to alpha members; a public install package is planned.

Because there is one implementation behind all three, an assistant connected over MCP cannot do anything your workspace role does not allow, and it sees the same validation errors a person would see on the website.

What an AI assistant can do with SAGOT

• Build an agent: write its instructions, greeting, voice, questions and boundaries, then validate and publish a version. Earlier versions stay available for rollback.
• Make calls: import contacts, check whether a number is eligible under your calling policy, and start a single call or a campaign.
• Read results: each call has a status, an agent-reported outcome, a transcript, a recording and any follow-up the agent scheduled.
• Connect actions: let the voice agent create bookings or records in your own systems through HTTPS connections you configure and approve.

Access and safety

• Workspace API keys are scoped and can be listed and revoked at any time; create a new key before revoking an old one to rotate without downtime.
• Calling windows, attempt limits, budgets and the AI disclosure in each greeting are enforced by the platform on every surface, not by the client.
• SAGOT keeps a platform do-not-call list that no workspace can call.

Frequently asked questions

Does SAGOT have an MCP server?

Yes. Any MCP client that supports Streamable HTTP can connect to https://sagots.com/mcp with a workspace API key and use every SAGOT operation as a tool.

Is the API the same as what the website uses?

Yes. The website, API, MCP server and CLI call the same operations with the same rules, so a workflow you build in the browser can be automated without a separate integration.

Can I use SAGOT today?

SAGOT is in a closed alpha. Join the waitlist on the home page; invited members get a workspace and can create API keys immediately.