Everything the console does, over MCP and REST
Agents, knowledge bases, phone numbers, calls, campaigns, contacts, deliveries and billing: one API, two ways in. Connect an AI assistant over MCP and build by talking, or call the REST API from your own code.
Add https://api.sinwan.ai/mcp to Claude, ChatGPT, Cursor or any MCP client. Sign in once with OAuth, then build agents, attach knowledge, buy numbers and read calls by talking. Guided playbooks are included as prompts.
Create an API key in the console and send it in the X-API-Key header. Every endpoint is under https://api.sinwan.ai/v1, documented in Swagger UI and an OpenAPI 3.1 spec with typed errors and cursor pagination.
After every call, the transcript, the summary and the fields you defined are delivered where you choose: a signed webhook, Google Sheets, HubSpot, or your own MCP server that the agent calls with the right tools.
Four steps to a first call
Get in
Create an API key in the console, or connect your MCP client and approve the OAuth consent.
Build an agent
Create it, write its instructions, attach a knowledge base and tools, then publish a version. Versions are immutable.
Call
Route a number to the published agent for inbound, or place an outbound call and read the transcript and analysis when it ends.
Two requests
The same workspace, the same agents, whichever door you use.
REST: list the workspace's agents
curl https://api.sinwan.ai/v1/agents \ -H "X-API-Key: tp_live_…"
MCP: a client configuration
{
"mcpServers": {
"sinwan": { "url": "https://api.sinwan.ai/mcp" }
}
}Every credential names what it may touch
An API key carries the scopes you chose when you created it; an OAuth grant carries the ones the user approved on the consent screen. Each domain has a read and a write scope. deliveries:write, the one that moves data out of the workspace, is never implied and must be named.
agents:readagents:writecalls:readcalls:writecampaigns:readcampaigns:writecontacts:readcontacts:writeleads:readleads:writeknowledge_bases:readknowledge_bases:writephone_numbers:readphone_numbers:writetools:readtools:writeworkflows:readworkflows:writemcp_servers:readmcp_servers:writenotifications:readnotifications:writetranscripts:readdeliveries:readdeliveries:writebilling:read
Reference
Before you integrate
Is there a sandbox?
No separate sandbox. A new workspace is the sandbox: build and publish agents for free, and pay per minute only when calls are placed. Unanswered calls cost nothing.
Which MCP clients work?
Any client that speaks Streamable HTTP with OAuth 2.1 dynamic client registration: Claude (desktop, web and Code), ChatGPT, Cursor and others. The server also accepts an X-API-Key header for clients that cannot run the OAuth flow.
Do you have an SDK?
Not yet. The OpenAPI 3.1 spec has operation ids and typed schemas for every operation, so a generated client works well, and most teams use the MCP server instead of writing code.
Can I bring my own telephony or AI keys?
Yes, for enterprise accounts: a SIP trunk or a Twilio account of your own, and your own OpenAI, Google or xAI keys. Write to sales@sinwan.ai.
Where does the data live?
On servers in Frankfurt, EU. Recordings, transcripts and form uploads stay there; the privacy chapter of the terms has the details.
Building something on top of sinwan?
Tell us what you are connecting. We will point you at the right tools, and add what is missing.