This page maps Vapi concepts onto Talqing fields, then lists the steps to move a working voice agent. Your prompt, provider accounts, phone numbers and tool endpoints carry over: Talqing is bring-your-own-key, numbers are imported from a carrier account you own, and an http operation calls any JSON API.

​
Concept mapping

​
Behaviour to plan for

  • Draft and published. Writes land on the draft; calls run the last published version. Publishing an agent pins each attached tool to its current published version, so republishing a tool alone changes nothing live. See versions.
  • Updates merge, lists replace. PATCH /v1/agents/{agent_id} merges objects key by key and null clears a field, but tools, handoffs, mcps and faqs replace whole. Unknown fields are refused. See agents overview.
  • Template tokens are checked at save. A {{token}} whose root is not userdata, vars or system_vars (in a prompt or greeting) is refused, so Vapi-style {{customer.number}} must be rewritten. See variables.
  • Inbound numbers need a published voice agent with no unsatisfiable variable. Assigning a number to an agent that declares a required var with no default is refused, because an inbound call supplies none.
  • Billing. Provider spend goes to your own accounts; Talqing charges a per-minute platform fee on voice and video and a per-message fee on text. See pricing and credits.

​
Migration steps

1

Add provider keys

Add a key for every provider your stack uses, including fallbacks. An agent whose provider has no key does not publish. See provider keys.
2

Recreate the agent

Paste the prompt and first message into prompt and greeting, replace Vapi template variables with {{vars.*}}, {{userdata.*}} or {{system_vars.*}}, and pick llm, stt and tts from GET /v1/catalog.
3

Rebuild each tool

Keep the argument schema; every property needs a description. Replace the server call with an http operation, and move reshaping or branching into code and if operations where that removes an endpoint. Validate and publish each tool — only published tools can be attached. See tools.
4

Validate and publish the agent

POST /v1/agents/{agent_id}/validate returns errors and warnings against the publish rules. Fix the errors, then POST /v1/agents/{agent_id}/publish. See validation.
5

Test before moving the number

Use Test call on the agent’s page in the dashboard, which runs the agent in your browser. Test calls are real, billable calls. Read each with GET /v1/calls/{session_id}: transcript, tool calls with outputs, and per-stage latency. See calls.
6

Import the number and assign the agent

Create and provision a carrier account, then import the number. Importing binds the number to Talqing at the carrier, so inbound calls stop reaching Vapi — do it when you are ready to cut over. Complete any outstanding setup_steps in the carrier console, assign the agent, and confirm readiness is live. See phone numbers.

​
Next

Core concepts

Agent, tool, task, conversation, call and session.

Inbound support line

A prompt, tools and a number answering calls, end to end.