For Agents
Programmatically create phone call, register phone call. Covers 29 operations with bearer authentication.
Use for: I need to phone call, I want to register phone call, Search for web call, Find all call
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
API for managing AI voice agents, phone calls, conversations, and more. The API exposes 29 endpoints secured with bearer authentication.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Retell AI API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fretellai.com%2Fretellai" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fretellai.com%2Fretellai" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Retell AI API.
Create phone call
Register phone call
Get call
List calls
Update call
Delete call
Patterns agents use Retell AI API for, with concrete tasks.
★ Communications Operations
Use the Retell AI API to perform communications operations programmatically. The API provides 29 endpoints covering core functionality including create phone call, register phone call, create web call.
Call POST /v2/create-phone-call to create phone call
Automated Agents Management
Automate agents operations by combining multiple Retell AI API endpoints. Agents can register phone call and then create web call in a single workflow.
Call POST /v2/register-phone-call to register phone call, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Retell AI API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'create phone call', load the operation schema, and execute with Jentic-managed credentials
29 endpoints — api for managing ai voice agents, phone calls, conversations, and more.
METHOD
PATH
DESCRIPTION
/v2/create-phone-call
Create phone call
/v2/register-phone-call
Register phone call
/v2/create-web-call
Create web call
/v2/get-call/{call_id}
Get call
/v2/list-calls
List calls
/v2/update-call/{call_id}
Update call
/v2/delete-call/{call_id}
Delete call
/v2/create-agent
Create voice agent
/v2/create-phone-call
Create phone call
/v2/register-phone-call
Register phone call
/v2/create-web-call
Create web call
/v2/get-call/{call_id}
Get call
/v2/list-calls
List calls
/v2/update-call/{call_id}
Update call
/v2/delete-call/{call_id}
Delete call
/v2/create-agent
Create voice agent
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Retell AI API by hand means learning its bearer token auth, targeting the api.retellai.com host, and coordinating call and agent lifecycle calls yourself. Through Jentic you install once, import Retell AI API from the API Directory, store the token once, and your agent calls it.
Permission scoping
Retell AI API puts the call id in the URL path (/v2/get-call/{call_id}), so a rule can pin your agent to one call: it can read and update that call and nothing else. You choose the operations it may call, so destructive ones like call deletion are not included unless you add them.
Credential isolation
Your Retell AI API token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a phone call' or 'get a call by id', and Jentic returns the matching Retell AI API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using Retell AI API through Jentic.
What authentication does the Retell AI API use?
The Retell AI API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I create phone call with the Retell AI API?
Yes. Use the POST /v2/create-phone-call endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Retell AI API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I create phone call through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create phone call'. Jentic returns the matching Retell AI API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Retell AI API have?
The Retell AI API exposes 29 endpoints covering agents, calls, knowledge base operations.
Can I limit what my agent is allowed to do with the Retell AI API?
Yes. Jentic One is self-hosted, so your own rules decide which Retell AI API operations and credentials your agent may use. Because this API puts the call id in the URL path, such as /v2/get-call/{call_id}, you can pin an agent to a single call so it only reads and updates that call and nothing else. You choose the operations it may run, so destructive ones like DELETE /v2/delete-call/{call_id} stay off limits unless you add them.
GET STARTED