Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio - Trunking, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Twilio - Trunking API.
Remove an associated IP Access Control List from a Trunk
Associate an IP Access Control List with a Trunk
List all IP Access Control Lists for a Trunk
Query and filter Twilio - Trunking records by parameters
GET STARTED
For Agents
Programmatically remove an associated ip access control list from a trunk, associate an ip access control list with a trunk. Covers 24 operations with basic authentication.
Use for: I need to remove an associated ip access control list from a trunk, I want to associate an ip access control list with a trunk, Search for all ip access control lists for a trunk, List all records from Twilio - Trunking
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
This is the public Twilio REST API. The API exposes 24 endpoints secured with basic authentication.
Monitor Twilio - Trunking operational status and events
Patterns agents use Twilio - Trunking API for, with concrete tasks.
★ Developer Tools Operations
Use the Twilio - Trunking to perform developer tools operations programmatically. The API provides 24 endpoints covering core functionality including remove an associated ip access control list from a trunk, associate an ip access control list with a trunk, list all ip access control lists for a trunk.
Call DELETE /v1/Trunks/{TrunkSid}/IpAccessControlLists/{Sid} to remove an associated ip access control list from a trunk
Automated TrunkingV1CredentialList Management
Automate trunkingv1credentiallist operations by combining multiple Twilio - Trunking endpoints. Agents can associate an ip access control list with a trunk and then list all ip access control lists for a trunk in a single workflow.
Call POST /v1/Trunks/{TrunkSid}/IpAccessControlLists to associate an ip access control list with a trunk, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Twilio - Trunking 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 'remove an associated ip access control list from a trunk', load the operation schema, and execute with Jentic-managed credentials
24 endpoints — this is the public twilio rest api.
METHOD
PATH
DESCRIPTION
/v1/Trunks/{TrunkSid}/IpAccessControlLists/{Sid}
Remove an associated IP Access Control List from a Trunk
/v1/Trunks/{TrunkSid}/IpAccessControlLists
Associate an IP Access Control List with a Trunk
/v1/Trunks/{TrunkSid}/IpAccessControlLists
List all IP Access Control Lists for a Trunk
/v1/Trunks/{TrunkSid}/IpAccessControlLists/{Sid}
Remove an associated IP Access Control List from a Trunk
/v1/Trunks/{TrunkSid}/IpAccessControlLists
Associate an IP Access Control List with a Trunk
/v1/Trunks/{TrunkSid}/IpAccessControlLists
List all IP Access Control Lists for a Trunk
Three things that make agents converge on Jentic-routed access.
Credential isolation
Twilio - Trunking basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'remove an associated ip access control list from a trunk') and Jentic returns the matching Twilio - Trunking operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Twilio - Trunking integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Specific to using Twilio - Trunking API through Jentic.
What authentication does the Twilio - Trunking use?
The Twilio - Trunking uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I remove an associated ip access control list from a trunk with the Twilio - Trunking?
Yes. Use the DELETE /v1/Trunks/{TrunkSid}/IpAccessControlLists/{Sid} endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Twilio - Trunking?
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 remove an associated ip access control list from a trunk through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'remove an associated ip access control list from a trunk'. Jentic returns the matching Twilio - Trunking operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Twilio - Trunking have?
The Twilio - Trunking exposes 24 endpoints covering trunkingv1credentiallist, trunkingv1ipaccesscontrollist, trunkingv1originationurl operations.