Build & deploy
voice, video & text agents
in minutes, not days
Let us worry about engineering, reliability & scalability, so that you can focus on building quality AI agents.
Hello. How can I help you today?
Cara · AnamOf course — let me pull that order up.
No more worrying about code and infrastructure
Describe the agent and publish it. We compile that definition and run the realtime session behind it.
Bring your own keys
Your provider accounts bill you directly, at your rates. Our platform fee stays small enough never to eat your gross margin.
Your team focuses on what matters
Prompts, tools, MCP servers, triggers and models — the decisions that actually decide whether an agent is any good.
Your own keys for
OpenAI
Gemini
xAI
Deepgram
ElevenLabs
Soniox
Sarvam
Raya
Anam
ai-coustics
Twilio
Plivo
Exotel
VobizChannels
One definition. Three ways to talk.
The prompt, the tools and the knowledge do not change when the channel does. Switching it changes which model slots the agent fills, not how it behaves.
Text
Chat on the same agent definition, over the API or an embedded widget, with the same tools behind it.
- Streamed replies over SSE
- Images in, grounded answers out
- Runs the same published version
Voice
A browser call or a real phone number, running either a speech pipeline you assemble yourself or a single realtime model.
- STT + LLM + TTS, or one realtime model
- Inbound and outbound PSTN on your carrier
- Recording and post-call analysis
Video
The same voice agent wearing an Anam avatar, so the person on the other end has a face to talk to.
- Anam avatars, picked per agent
- Identical prompt, tools and knowledge
- Browser sessions, no plugin
Capabilities
Everything you would have written by hand.
Build it yourself in the dashboard, hand it to Copilot and review what changed, or drive the whole thing from Claude Code over MCP. Same agent either way.
Model stack
System prompt
You handle refund requests for Northwind. Confirm the order number before you look anything up, and never promise a refund the policy does not allow. You are speaking with {{userdata.name}}.
Knowledge
- Returns & refunds policy18 pages
- Northwind help centre204 pages
Tools
- look_up_orderHTTP
- refund_policyKnowledge
- issue_refundCode
- transfer_to_humanHandoff
Tools that do real work
HTTP requests, code steps, conditions, generated replies, frontend actions, MCP operations, handoffs and end-call — composed as a tree, not a script.
Knowledge the agent can cite
Crawl a site, review what was extracted, and attach the result so the agent fetches grounded context mid-conversation.
Phone numbers, your carrier
Connect Twilio, Plivo, Exotel or Vobiz, import your DIDs, and point inbound calls at a published agent. PSTN billing stays with the carrier.
Copilot in every editor
An AI builder that can rewrite the prompt, swap models, add tools, build knowledge and publish — and shows you exactly what it changed.
Sessions you can audit
Transcript, tool invocations, final userdata, per-provider usage and a cost breakdown for every session — test runs included.
API and MCP, not just a UI
Every dashboard action is an API operation, and the same set is exposed over MCP — so Claude Code or Codex can build the agent with you.
Platform fee
One flat fee. Nothing on text.
Talqing is strict bring-your-own-keys, so model, speech, avatar and carrier costs go straight to your own accounts at your own rates. A per-minute platform fee is the only thing we add on top — and it is the only thing we ever charge you for.
Text
Free
Every conversation and every message, on the API or the widget. There is no per-minute meter on text at all.
Voice
₹0.50per minute
Browser calls and phone calls alike. Your carrier bills the PSTN leg; we bill the agent that ran on it.
Video
₹1per minute
The same voice agent with an Anam avatar attached, billed for the minutes the avatar is on screen.
Discounts are available at committed volume on both voice and video.
Talk to us about volumeFAQ
Questions we get
before the first call.
Something not covered here? Write to us — a person answers.
What can I build with Talqing?
Voice, video and text agents that talk to your users, call tools, retrieve knowledge, fire webhooks, capture session state and hand off to other agents. Realtime voice is the centre of gravity; the same agent model also runs unattended tasks that take typed inputs and return a typed result.
Do I need to write LiveKit Agents code?
No. You author the agent in the dashboard, through Copilot, or over MCP from your own editor. Talqing compiles that definition into a LiveKit AgentSession and runs it on the platform runtime.
Whose API keys does it use?
Yours. Talqing is strict bring-your-own-keys: you connect your own OpenAI, Gemini, xAI, Deepgram, ElevenLabs, Soniox, Sarvam and Anam accounts, and those providers bill you directly. We never resell tokens or minutes — the per-minute platform fee is the whole of what we charge.
Can I test an agent before publishing?
Yes. Run browser voice, video and text sessions from the dashboard, then read the transcript, tool calls, captured fields, provider usage and cost for that session before you publish anything.
How do tools work without code?
A tool is an operation tree. You compose HTTP requests, conditional branches, code steps, generated replies, frontend actions, MCP and provider operations, handoffs, end-call and webhook triggers from the editor — and there is a code operation for the cases that genuinely need one.
Can the agent use my product knowledge?
Yes. Crawl a site into a knowledge base, review the pages and structure that were extracted, then attach the base to an agent so runtime calls can fetch grounded context.
Is telephony included?
Yes, on your own carrier account — Twilio, Plivo, Exotel or Vobiz. Connect the account under Phone Numbers, import your DIDs, assign a published voice agent for inbound, and place outbound calls from the dashboard. PSTN charges stay with your carrier; Talqing runs the agent.
Your first agent
is one prompt away.
Sign in with Google, tell it what the job is, and place a test call before your coffee goes cold.