config, sent to POST /v1/agents. It decides the channel, the models, what the agent says and what it can do. Tools, MCP servers, FAQs and handoff targets are attached by id inside it. Phone numbers, web call tokens, chats and campaigns all point at an agent.
name is required; every other field has a default. The tool id must be a published tool from GET /v1/tools.
Config reference
“Channels” is where a field has an effect. Outside its channels a field is cleared on save, or refused if you switched it on. See channels.
An unknown field is refused, not ignored. Defining a tool, MCP server or FAQ inline on
POST/PATCH /v1/agents creates it as a stored object and saves its id; on a call request it lasts for that call only (per-call configuration).
Updating an agent
PATCH /v1/agents/{agent_id} takes only the fields you change:
get, create and update return the same shape. Some fields are normalized on save (switching to text clears the speech stack; setting realtime clears the cascade), so read the response rather than assuming your input survived.
Every write lands on the draft; live traffic runs the last published version, and publishing pins each attached tool’s version. See versions and validation.
In the dashboard, agents are at https://app.talqing.com/agents; the editor opens at /agents/detail?id=<agent id>, with a cost estimate, a test call panel and the CoPilot beside it.
Next
Channels
What voice, video and text each have, and what switching clears.
Models
The catalog, the model slots and their settings.