Skip to main content
POST
cURL

Authorizations

Authorization
string
header
required

Send your API key as Authorization: Bearer YOUR_API_KEY.

Query Parameters

locationId
string
required

The sub-account. It must belong to the agency, and be the credential’s own sub-account when the credential is limited to one.

Body

application/json

One of three shapes: { id, mode: generate, information, agentType?, name?, voiceId? } to have AI write the agent, { id, mode: template, agentType?, name?, voiceId? } for a free starter draft, or { id, brainTemplateId, values?, name? } for a Brain template.

USD 0.50 per agent and campaign created, paid from the agency’s existing wallet balance. Clarification replies and failed builds are free.

id
string
required

A request id you choose and keep. Reuse it to read progress, to retry and to answer questions. The new agent’s own id comes back as agentId.

Pattern: ^[a-zA-Z0-9_-]{8,100}$
mode
any
required

generate: AI writes the agent from information. It costs USD 0.50, charged only once the agent and campaign are created.

information
string
required

The business information and the job the agent should do. Include website findings as text. This request never reads websites itself. On needs_information, send the extra facts with the same id. Facts already given are kept.

Required string length: 1 - 50000
name
string

The name the agent says on calls, not only a dashboard label. Use the name the user asked for exactly. Add a business name to it only when the user asked for that as part of the spoken name. Reuse a name already agreed for follow-up or batch builds with the same settings. Omit it only when no name was given. The agent is then called Tars.

Required string length: 1 - 100
voiceId
string

Optional. A voice id from GET /api/tfu-live-agents/voices. Defaults to cedar. Voice ids from GET /api/agent-builder/voices are for Agent Builder agents and are not accepted.

Required string length: 1 - 100
agentType
enum<string>

The main use, as the user states it or as an existing role they describe. Do not infer it from the business website or the type of business alone. If it is missing, generation returns needs_information before it builds or charges anything. Then ask the user which calls will make up most of the agent’s work.

Available options:
inbound_receptionist,
outbound_sales

Response

Successful TFU Live response. Setup acceptance is not verified readiness or campaign activation.

success
any
required
data
object
required