Integration

Rounded integration

Rounded (callrounded.com) runs AI voice agents that answer and place phone calls. Create, configure, deploy and delete agents and their post-call analysis questions, start outbound calls or stage inbound SIP calls, read call transcripts, extracted variables, post-call answers and recordings, hang up live calls, add or remove knowledge base sources, and route phone numbers to agents. Not exposed: changing an agent's conversation states after creation (custom-function headers and parameters, which can hold credentials, are never returned, so states read and written back would erase them; use Rounded Studio) and the older private-beta v0 call route; the API has no route to list agents or knowledge bases or to create a knowledge base. Authentication is an API key created in Rounded Studio (profile settings, API Keys), sent in the X-Api-Key header.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Rounded.Built from the 23 Rounded tools below, on the connection you add once.

What you can do with Rounded

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Call, 7 operations

  • delete_callDelete callDELETEAgents: ask firstDeletes a call (phone or web) and its record by id. Answers with an empty body on success.
  • get_callGet callGETAgents: ask firstReturns one call: status, timing, cost estimate in EUR, transcript, extracted variable values, post-call answers and, for phone calls, numbers, direction and recording_url. Personal data.
  • list_callsList callsGETAgents: ask firstLists phone and web calls, filtered by agent, type, numbers or start time. Cursor pagination by default (next_cursor); limit up to 1000. Transcripts and variable values only on request. Holds callers' phone numbers.
  • stage_sip_callStage sip callPOSTAgents: ask firstPrepares an agent for an inbound SIP call before it arrives and returns data.call_id; your SIP INVITE must carry it in the X-Rounded-Call-Id header. Pass sync true to wait until the call is staged (HTTP 408 on timeout).
  • start_phone_callStart phone callPOSTAgents: ask firstPlaces a real outbound phone call now from one of your Rounded numbers to to_number, handled by agent_id; the call is billed (see cost on get_call). Returns data.call_id; follow the call with get_call.
  • terminate_callTerminate callPOSTAgents: ask firstHangs up an ongoing phone call immediately, ending it for the person on the line. Web calls are not supported.
  • update_call_metadataUpdate call metadataPATCHAgents: ask firstAdds metadata to a call: by default merged into its existing metadata; override true replaces it entirely. Returns the updated call.

Agent, 5 operations

  • create_agentCreate agentPOSTAgents: ask firstCreates a voice agent (name and language required; prompt, conversation states, voice, LLM, webhook optional) and returns its configuration with data.id. Calls reach it through start_phone_call or a number set with update_phone_number.
  • delete_agentDelete agentDELETEAgents: ask firstPermanently deletes an agent and all its configuration versions; the vendor says this cannot be undone.
  • deploy_agentDeploy agentPOSTAgents: ask firstPublishes a configuration version of an agent (default: the latest draft), making it live at once for the agent's phone and web calls. Returns the deployed version and configuration_id.
  • get_agentGet agentGETAgents: ask firstReturns an agent's configuration: prompts, states, variables, voice, LLM, transcriber and webhook settings. Without version, the latest published one. Custom-function headers and parameters are never returned.
  • update_agentUpdate agentPATCHAgents: ask firstChanges an agent's settings; send only the fields to change. name, webhook_url, webhook_subscriptions and secure_recording_urls apply at once; any other change creates a new draft version that goes live with deploy_agent.

Post call question, 5 operations

  • create_post_call_questionsCreate post call questionsPOSTAgents: ask firstAdds up to 50 post-call questions to an agent in one call; each needs name, description (the prompt) and type. Selector types need at least 2 options. Answers appear in post_call_answers on get_call.
  • delete_post_call_questionDelete post call questionDELETEAgents: ask firstDeactivates a post-call question (soft_delete true, the default) or deletes it for good (soft_delete false); Rounded then stops answering it after calls.
  • get_post_call_questionGet post call questionGETAgents: ask firstReturns one post-call question of an agent: name, description (the prompt), type, options, examples, whether it is active and its timestamps.
  • list_post_call_questionsList post call questionsGETAgents: ask firstLists an agent's post-call questions, which Rounded answers from each call after it ends: name, description (the prompt), type, options, examples and whether each is active.
  • update_post_call_questionsUpdate post call questionsPATCHAgents: ask firstUpdates up to 50 post-call questions of an agent; only description changes. Each item needs id, name, description and type, so read them with get_post_call_question first. An item without id creates a new question.

Knowledge base source, 2 operations

  • add_knowledge_base_sourcesAdd knowledge base sourcesPOSTAgents: ask firstAdds a PDF file and/or text sources to a knowledge base, which agents using it answer from. Returns the knowledge base with its sources and its status (ready or ingesting).
  • delete_knowledge_base_sourcesDelete knowledge base sourcesDELETEAgents: ask firstRemoves sources from a knowledge base by id (sources[].id from get_knowledge_base); agents stop answering from them. Returns the knowledge base with its remaining sources.

Phone number, 2 operations

  • list_phone_numbersList phone numbersGETAgents: ask firstLists your organization's phone numbers (PSTN or SIP trunk): number, name, the agent answering inbound calls, redirect settings and SIP URI and usernames. Page-based by default; limit up to 1000.
  • update_phone_numberUpdate phone numberPATCHAgents: ask firstChanges how a phone number handles live calls: its name, the agent answering inbound calls, or a redirect of every call to another number (overrides the agent). Send only the fields to change.

Agent version, 1 operation

  • list_agent_versionsList agent versionsGETAgents: ask firstLists every configuration version of an agent, drafts and published: version number, configuration_id, created_at and the active flag. Pass a version to get_agent or deploy_agent.

Knowledge base, 1 operation

  • get_knowledge_baseGet knowledge baseGETAgents: ask firstReturns a knowledge base with its status (ready or ingesting) and its sources (file or text, with id, name or title and URL). Knowledge bases are created in Rounded Studio; no tool lists them.

Use Rounded from Claude Code, Cursor or Codex

Connect Rounded in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Rounded operations become tools the client can call, next to every other integration you connected.

Claude Code
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"
Codex (~/.codex/config.toml)
[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"
Cursor, Claude Desktop and other JSON configs
{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Rounded

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect Rounded once

    Add your Rounded connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. Describe the job in chat

    The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Rounded integration FAQ

What can you do with the Rounded integration?

LiveContext exposes 23 operations on Rounded, covering call, agent, post call question and knowledge base source.

Popular integrations

Browse the whole catalog