Twilio - Intelligence
Browse all Twilio APIs★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource Controlbasic27 EndpointsREST
For Agents
Programmatically create a new custom operator for the given account, retrieves a list of all custom operators for an account.. Covers 27 operations with basic authentication.
Use for: I need to a new custom operator for the given account, I want to retrieves a list of all custom operators for an account., Search for a specific custom operator., Find all fetch a specific custom operator.
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
This is the public Twilio REST API. The API exposes 27 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the Twilio - Intelligence to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio - Intelligence, 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.
1
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%2Ftwilio.com%2Ftwilio---intelligence" | sh2
Step 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%2Ftwilio.com%2Ftwilio---intelligence" | 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.
Capabilities
What an agent can do with Twilio - Intelligence API.
Create a new Custom Operator for the given Account
Retrieves a list of all Custom Operators for an Account.
Update a specific Custom Operator.
Fetch a specific Custom Operator.
Delete a specific Custom Operator.
Get download URLs for media if possible
Use Cases
Patterns agents use Twilio - Intelligence API for, with concrete tasks.
★ Developer Tools Operations
Use the Twilio - Intelligence to perform developer tools operations programmatically. The API provides 27 endpoints covering core functionality including create a new custom operator for the given account, retrieves a list of all custom operators for an account., update a specific custom operator..
Call POST /v2/Operators/Custom to create a new custom operator for the given account
Automated IntelligenceV2CustomOperator Management
Automate intelligencev2customoperator operations by combining multiple Twilio - Intelligence endpoints. Agents can retrieves a list of all custom operators for an account. and then update a specific custom operator. in a single workflow.
Call GET /v2/Operators/Custom to retrieves a list of all custom operators for an account., then verify the result
AI Agent Integration via Jentic
AI agents discover and call Twilio - Intelligence 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 basic tokens manually.
Search Jentic for 'create a new custom operator for the given account', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
27 endpoints — this is the public twilio rest api.
METHOD
PATH
DESCRIPTION
POST
/v2/Operators/Custom
Create a new Custom Operator for the given Account
GET
/v2/Operators/Custom
Retrieves a list of all Custom Operators for an Account.
POST
/v2/Operators/Custom/{Sid}
Update a specific Custom Operator.
GET
/v2/Operators/Custom/{Sid}
Fetch a specific Custom Operator.
DELETE
/v2/Operators/Custom/{Sid}
Delete a specific Custom Operator.
GET
/v2/Transcripts/{Sid}/Media
Get download URLs for media if possible
GET
/v2/Operators/{Sid}
Fetch a specific Operator. Works for both Custom and Pre-built Operators.
GET
/v2/Operators
Retrieves a list of all Operators for an Account, both Custom and Pre-built.
POST
/v2/Operators/Custom
Create a new Custom Operator for the given Account
GET
/v2/Operators/Custom
Retrieves a list of all Custom Operators for an Account.
POST
/v2/Operators/Custom/{Sid}
Update a specific Custom Operator.
GET
/v2/Operators/Custom/{Sid}
Fetch a specific Custom Operator.
DELETE
/v2/Operators/Custom/{Sid}
Delete a specific Custom Operator.
GET
/v2/Transcripts/{Sid}/Media
Get download URLs for media if possible
GET
/v2/Operators/{Sid}
Fetch a specific Operator. Works for both Custom and Pre-built Operators.
GET
/v2/Operators
Retrieves a list of all Operators for an Account, both Custom and Pre-built.
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Twilio Intelligence by hand means setting up HTTP basic auth with your Account SID and Auth Token, pointing at the intelligence.twilio.com host, and handling pagination and retries across operator and transcript operations yourself. Through Jentic you install once, import Twilio Intelligence from the API Directory, store the Account SID and Auth Token once, and your agent calls it.
Permission scoping
Twilio Intelligence puts the operator and transcript ids in the URL path (/v2/Operators/{Sid}, /v2/Transcripts/{Sid}/Media), so a rule can pin your agent to one operator: it can read or update that operator and nothing else. You choose the operations it may call, so destructive ones like deleting a custom operator are not included unless you add them.
Credential isolation
Your Twilio Account SID and Auth Token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create a custom operator for the account', and Jentic returns the matching Twilio Intelligence operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Twilio - Intelligence API through Jentic.
What authentication does the Twilio - Intelligence use?
The Twilio - Intelligence uses HTTP Basic authentication with username and password. 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 a new custom operator for the given account with the Twilio - Intelligence?
Yes. Use the POST /v2/Operators/Custom endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Twilio - Intelligence?
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 a new custom operator for the given account through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'create a new custom operator for the given account'. Jentic returns the matching Twilio - Intelligence operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Twilio - Intelligence have?
The Twilio - Intelligence exposes 27 endpoints covering intelligencev2customoperator, intelligencev2media, intelligencev2operator operations.
Can I limit what my agent is allowed to do with the Twilio Intelligence API?
Yes. Because you run Jentic One yourself, self-hosted, your own rules decide which Twilio Intelligence operations and credentials the agent can use. Since the operator and transcript IDs sit in the URL path, such as /v2/Operators/{Sid} and /v2/Transcripts/{Sid}/Media, a rule can pin the agent to a single operator so it can read or update that one and nothing else. You also pick the operations it may call, so destructive ones like deleting a custom operator stay out unless you add them.
GET STARTED