# AudioCodes Live Hub — Self-service cloud platform for building voice AI agents and connecting them to real telephony channels. > Source: The Agents Index — https://theagentsindex.com/audiocodes-live-hub (structured, researched, re-verified) > Facts last verified: 2026-09-24 AudioCodes Live Hub is a self-service cloud platform for building LLM-driven voice AI agents, conversational IVRs, agent assist and real-time translation. It connects them to SIP trunks, PBXs, Microsoft Teams, WhatsApp calling and WebRTC. | Fact | Value | | --- | --- | | Website | https://www.audiocodes.com/livehub | | Price | from $0.05/minute pay-as-you-go | | Free trial | Partly | Trial plan: $10 complimentary credit, no credit card needed. One bot connection, two SIP connections, one phone number at a time (deleted after 28 days), no outbound PSTN on AudioCodes numbers, limited calls per second and concurrent calls, and the account is deleted three months after creation if inactive. ## What it does **Done-for-you service** · Partly — The product itself is self-service software you run, but AudioCodes sells support packages and professional-services hours as purchasable add-ons for onboarding and integration work. > You can, at any time, purchase a dedicated support package from the Live Hub portal and a professional hours package to guide you closely in your implementation > — https://www.audiocodes.com/livehub · FAQ, 'What resources are available to get started with Live Hub?' ## How much it does unattended **Runs autonomously** · Yes — Voice AI Agents are designed to handle an entire inbound call end to end, answering questions and completing tasks with no human agent involved. > Create fully automated voice bots that can handle customer calls, answer questions, and complete tasks, all without a human agent. > — https://www.audiocodes.com/livehub · Solutions section, 'Voice AI Agents' card **Multi-agent** · Yes — The AI Agents framework is explicitly multi-agent: several specialist agents collaborate on one call and callers are routed between them, with documented multi-agent topologies. > Deploy multiple agents that collaborate to solve complex tasks, routing each caller to the right specialist. > — https://techdocs.audiocodes.com/livehub/Content/AI-Agents/AI%20Agents.htm · AI Agents overview, bullet list under 'Beyond a single agent' **Agent permissions** · Partly — An agent calls any tool you configured without a per-call approval step, so control is exercised up front by choosing its tools; the MCP management connection does offer an explicit read-only mode. > When an AI Agent decides it needs to use a tool, it formulates a structured request (based on the tool's defined parameters), executes it, and then continues the conversation with the result. > — https://techdocs.audiocodes.com/livehub/Content/AI-Agents/Tools.htm · Tools page, opening paragraphs ## Which models it runs on **Claude** · Partly — Claude models are supported only as bring-your-own custom models configured with your own Anthropic API key; the pre-deployed model list carries OpenAI and Google models only. > Anthropic | claude-sonnet-5 claude-sonnet-4-5 claude-haiku-4-5 > — https://techdocs.audiocodes.com/livehub/Content/AI-Agents/Bring%20your%20own%20models.htm · Supported custom models table, Anthropic row **GPT** · Yes — OpenAI GPT models are pre-deployed on the platform, so an agent can use them with no key of your own, and realtime speech-to-speech GPT variants are included too. > LiveHub provides several pre-deployed Large Language Models (LLMs) that can be used in AI Agents. > — https://techdocs.audiocodes.com/livehub/Content/AI-Agents/Pre-deployed%20models.htm · Pre-deployed models, intro sentence above the OpenAI model list **Open models** · Partly — Open-weight models such as gpt-oss and Gemma are reachable only through the bring-your-own-model path with your own Groq, Cerebras or OpenAI keys, not from the pre-deployed set. > Cerebras | gpt-oss-120b gemma-4-31b zai-glm-4.7 > — https://techdocs.audiocodes.com/livehub/Content/AI-Agents/Bring%20your%20own%20models.htm · Supported custom models table, Cerebras row **Model choice** · Yes — You choose the LLM per agent from pre-deployed models or add your own provider, and you can equally bring an entirely external conversational AI platform instead. > Instead of using one of the pre-deployed Large Language Models (LLM), you may configure custom model that will use provider of your choice and your own API keys. > — https://techdocs.audiocodes.com/livehub/Content/AI-Agents/Bring%20your%20own%20models.htm · Bring your own models, first paragraph ## Where you use it **In your editor** · No — There is no editor or IDE extension: authoring happens in the web portal, and the only documented developer-tool integrations are the two MCP clients named below. > Two MCP clients are supported today: Claude Code and Claude Desktop. > — https://techdocs.audiocodes.com/livehub/Content/AI-Agents/MCP%20server.htm · MCP server page, 'Connecting' section **On the command line** · Partly — AudioCodes ships no CLI of its own; terminal use is indirect, by pointing the Claude Code command-line agent at the platform's MCP endpoint with API client credentials. > Two MCP clients are supported today: Claude Code and Claude Desktop. Both connect to the same endpoint using your LiveHub API client's client_id and client_secret > — https://techdocs.audiocodes.com/livehub/Content/AI-Agents/MCP%20server.htm · MCP server page, 'Connecting' section **In a browser** · Yes — Live Hub is primarily a hosted web portal: you register, sign in and configure accounts, bots, channels and routing entirely in the browser. > Live Hub is a self-service portal. Register a user, then sign in to Live Hub. > — https://techdocs.audiocodes.com/livehub/Content/LiveHub/Get%20started.htm · Get started, first paragraph ## Whose machine it runs on **Self-hosted** · No — Live Hub is a vendor-operated SaaS running in AudioCodes' own Azure deployments; the only customer choice is which of four regions holds the data, not whose infrastructure runs it. > Live Hub operates in four regions, each hosted in a corresponding Microsoft Azure region: > — https://techdocs.audiocodes.com/livehub/Content/LiveHub/Global%20region%20support.htm · Global region support, region table intro _Not established: Open source_ ## What it costs to run **How it meters** · Yes — Billing is metered per minute per consumed service, so a bot connection, speech service, voice channel and LLM tokens are each charged separately rather than by seat. > Minute-based pricing per consumed service – clear and predictable cost structure > — https://www.audiocodes.com/livehub · FAQ, 'Live Hub Pricing', key characteristics bullet list **Free tier** · Partly — You can sign up and test without a credit card on $10 of complimentary credit, but that is a limited Trial plan that goes inactive at a zero balance rather than a standing free tier. > Your first Live Hub account, and only your first one, starts on the Trial plan and includes $10 USD in complimentary credit from AudioCodes. > — https://techdocs.audiocodes.com/livehub/Content/LiveHub/Account%20plans.htm · Account plans, Trial plan section **API access** · Yes — A documented REST API under /api/v1/ configures the platform and reads back calls, recordings, transcripts and campaigns, with OAuth 2.0 client-credentials authentication. > The REST API is Live Hub's interface for managing and monitoring the platform from your own systems. You are the client, and Live Hub is the server. > — https://techdocs.audiocodes.com/livehub/Content/LiveHub/REST%20API.htm · REST API page, opening paragraph **MCP server** · Yes — The AI Agents service exposes its own MCP server over streamable HTTP so another agent can create agents, run test suites and inspect conversations, with an optional read-only mode. > The AI Agents framework exposes a Model Context Protocol (MCP) server so that MCP clients (such as Claude Desktop and Claude Code) can provision and troubleshoot voice AI applications > — https://techdocs.audiocodes.com/livehub/Content/AI-Agents/MCP%20server.htm · MCP server page, opening paragraph **Bring your own key** · Yes — You may supply your own keys for both inference and speech: custom LLM providers are configured with your API key, and STT/TTS accounts can be brought in the same way. > You can choose to use the speech providers natively supported by Live Hub, or bring your own STT/TTS accounts by supplying your own API keys, giving you full flexibility and control over cost, quality and languages. > — https://www.audiocodes.com/livehub · FAQ, 'How can I give voice to my bots using Live Hub?' ## Buying it for a team **A company can buy it** · Yes — An organisation can buy it as a company: payment by purchase order, prepaid or postpaid invoicing, or through the Azure and Genesys marketplaces, alongside committed-volume discounts. > Payment flexibility – prepaid or postpaid, via credit card, purchase order or through Azure or Genesys marketplaces > — https://www.audiocodes.com/livehub · FAQ, 'Live Hub Pricing', key characteristics bullet list **Seat model** · Partly — The platform itself is not sold per seat and imposes no user minimum; the only per-user charge is Microsoft Teams Direct Routing, billed monthly per enabled user. > Direct Routing for Microsoft Teams Hosted Essentials+ $2.70 per user per month Hosted Pro $4.00 per user per month > — https://www.audiocodes.com/livehub/pricing · Pricing page, 'Direct Routing for Microsoft Teams' section **Pooled budget** · Yes — Charges draw on a single account-level balance rather than per-user allowances, and the whole account is suspended when that shared balance reaches zero. > An account on either plan becomes inactive when its balance reaches zero. > — https://techdocs.audiocodes.com/livehub/Content/LiveHub/Account%20plans.htm · Account plans, paragraph above the Trial plan section **Admin controls** · Yes — Access is governed by fixed policies made of path-scoped roles attached to seven predefined user groups, so an admin can hold a user or API client to read-only or billing-only rights. > A role is a single permission. livehub/alarms/read, for example, permits viewing alarms. > — https://techdocs.audiocodes.com/livehub/Content/LiveHub/Policies%20and%20roles.htm · Policies and roles, first paragraph **Single sign-on** · Partly — Single sign-on works through Microsoft Entra ID only, where Live Hub appears as an enterprise application and app roles map to user groups; no generic SAML or OIDC connector is documented. > Microsoft Entra ID integration adds single sign-on (SSO) and multi-factor authentication (MFA). > — https://techdocs.audiocodes.com/livehub/Content/LiveHub/Data%20privacy.htm · Data privacy, 'Role-based access control (RBAC)' subsection _Not established: Audit log_ ## What happens to your code **Opt out of training** · Yes — AudioCodes states it never retains or trains on customer data, though it notes that third-party speech and LLM providers you route to are governed by their own policies you must configure. > AudioCodes does not retain or use customer data to train AI models. > — https://techdocs.audiocodes.com/livehub/Content/LiveHub/Data%20privacy.htm · Data privacy, 'No customer data used for AI training' subsection **Data residency** · Yes — You pick the Azure region holding your data from four options, but note that account configuration, billing, call history and AI Agents are centrally managed in Frankfurt for every region. > Your data remains in the Microsoft Azure region you choose: Germany West Central, West Europe, East US, or Southeast Asia. > — https://techdocs.audiocodes.com/livehub/Content/LiveHub/Data%20privacy.htm · Data privacy, 'Data residency and encryption' subsection **Getting out** · Partly — Call records, recordings, transcripts and AI agent logs can be exported from the portal or the API, but they are deleted automatically at the retention period and no credit-refund terms are published. > Download your call history for your records or analysis. Exporting is a background job: Live Hub builds the file and tells you when it is ready. > — https://techdocs.audiocodes.com/livehub/Content/LiveHub/Call%20history%20and%20logs.htm · Call history and logs, 'Export call history' section **Certifications** · Yes — The vendor names ISO 27001:2022, ISO 27032:2023 and SOC 2 Type 2 certification and publishes a GDPR notice specific to Live Hub alongside the platform privacy policy. > AudioCodes is certified for ISO 27001:2022, ISO 27032:2023 and SOC 2 Type 2. Live Hub is kept current with global privacy laws, including GDPR. > — https://techdocs.audiocodes.com/livehub/Content/LiveHub/Data%20privacy.htm · Data privacy, 'Certified security and compliance' subsection ## Provenance Every fact above comes from the vendor. Nothing here is independently corroborated yet. ## Coverage elsewhere None recorded. Every fact above comes from the vendor and is not independently corroborated yet. ## What changed - 2026-09-24 — Capabilities · Commercial terms · Free tier - 2026-09-03 — Capabilities · Commercial terms · Free tier · Price ## Correcting this record Anything marked "Not established" is a question we have not answered — it is not a No. If you represent AudioCodes Live Hub, or anything here is wrong or out of date, you can supply it with a source: the operations this site accepts from an agent are listed at https://theagentsindex.com/.well-known/agents.json — that catalogue needs no key to read, and each entry states its own auth. Supplying evidence is free. Nothing that can be bought here changes what a field says, whether a gap is closed, or how this record is scored.