Agents usage is billed at the current Agents rate. Managed telephony is
metered separately. Sandbox API keys never bill, but production Agent calls
require a funded live account.
1
Open the Agent builder
Go to Launch an Agent.
Sign up or sign in. The path is preserved through authentication.
2
Describe the job
Choose a template or start blank. Set the agent’s persona, greeting,
language, voice, and the rules it must follow.
3
Connect knowledge and tools
Add the information the agent should answer from. Bind tools when the agent
needs to look up data or take an action. Keep sensitive credentials in
server-side tool configuration.
4
Test before assigning a number
Run the browser greeting test. Confirm that the opening line, voice, and
first response match your instructions. Test transfer and consent behavior
when your workflow uses them.
5
Connect a phone number
Assign an available managed number or connect a supported carrier route.
Availability and regulatory onboarding vary by country. Live calls consume
Agents usage plus any managed telephony usage.
Agents Beta or Omni API?
Choose Agents Beta when you want a console workflow for configuration, testing, and phone setup. Choose the Omni API when your application needs to open realtime sessions and control the fullconfigure frame in code. Both use
the same Omni realtime engine.
Next steps
Agent greetings
Set the first line and recording consent behavior.
Omni tools
Connect hosted, server, or client tools.
Pricing and metering
Understand Agents and telephony usage.
Build with the API
Use an instant sandbox key and make your first request.