Developer ToolsSource Controlbasic31 EndpointsREST
For Agents
Programmatically retrieve a list of billing periods for a super sim., order an esim profile.. Covers 31 operations with basic authentication.
Use for: I need to a list of billing periods for a super sim., I want to order an esim profile., Search for a list of esim profiles., Find all fetch an esim profile.
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
This is the public Twilio REST API. The API exposes 31 endpoints secured with basic authentication.
Install Jentic One Beta
Connect the Twilio - Supersim to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Twilio - Supersim, 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---supersim" | 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---supersim" | 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 - Supersim API.
Retrieve a list of Billing Periods for a Super SIM.
Order an eSIM Profile.
Fetch an eSIM Profile.
Create a Fleet
Updates the given properties of a Super SIM Fleet instance from your account.
Use Cases
Patterns agents use Twilio - Supersim API for, with concrete tasks.
★ Developer Tools Operations
Use the Twilio - Supersim to perform developer tools operations programmatically. The API provides 31 endpoints covering core functionality including retrieve a list of billing periods for a super sim., order an esim profile., retrieve a list of esim profiles..
Call GET /v1/Sims/{SimSid}/BillingPeriods to retrieve a list of billing periods for a super sim.
Automated SupersimV1BillingPeriod Management
Automate supersimv1billingperiod operations by combining multiple Twilio - Supersim endpoints. Agents can order an esim profile. and then retrieve a list of esim profiles. in a single workflow.
Call POST /v1/ESimProfiles to order an esim profile., then verify the result
AI Agent Integration via Jentic
AI agents discover and call Twilio - Supersim 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 'retrieve a list of billing periods for a super sim.', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
31 endpoints — this is the public twilio rest api.
METHOD
PATH
DESCRIPTION
GET
/v1/Sims/{SimSid}/BillingPeriods
Retrieve a list of Billing Periods for a Super SIM.
POST
/v1/ESimProfiles
Order an eSIM Profile.
GET
/v1/ESimProfiles
Retrieve a list of eSIM Profiles.
GET
/v1/ESimProfiles/{Sid}
Fetch an eSIM Profile.
POST
/v1/Fleets
Create a Fleet
GET
/v1/Fleets
Retrieve a list of Fleets from your account.
POST
/v1/Fleets/{Sid}
Updates the given properties of a Super SIM Fleet instance from your account.
GET
/v1/Fleets/{Sid}
Fetch a Fleet instance from your account.
GET
/v1/Sims/{SimSid}/BillingPeriods
Retrieve a list of Billing Periods for a Super SIM.
POST
/v1/ESimProfiles
Order an eSIM Profile.
GET
/v1/ESimProfiles
Retrieve a list of eSIM Profiles.
GET
/v1/ESimProfiles/{Sid}
Fetch an eSIM Profile.
POST
/v1/Fleets
Create a Fleet
GET
/v1/Fleets
Retrieve a list of Fleets from your account.
POST
/v1/Fleets/{Sid}
Updates the given properties of a Super SIM Fleet instance from your account.
GET
/v1/Fleets/{Sid}
Fetch a Fleet instance from your account.
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
T
Twilio - Supersim
- Non-Ready (F)37/100
82
Foundational Compliance60
Developer Experience & Jentic Compatibility41
AI-Readiness & Agent Experience94
Agent Usability10
Security54
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
82
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
30%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
60
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: B-Signals: 4
23%
Example Density
How richly the API is illustrated with examples.
93%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
41
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: D-Signals: 4
45%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
17%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
10
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
10%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
54
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: CSignals: 1
54%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Twilio Super SIM by hand means setting up HTTP basic auth with your account SID and auth token against the supersim.twilio.com host and handling retries yourself. Through Jentic you install once, import Twilio Super SIM from the API Directory, store the account SID and auth token once, and your agent calls it.
Permission scoping
Twilio Super SIM puts the SIM, fleet, and eSIM profile Sids in the URL path (/v1/Fleets/{Sid}), so a rule can pin your agent to one fleet or SIM. You choose the operations it may call, so writes like updating a fleet 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 'list billing periods for a SIM' or 'create a fleet', and Jentic returns the matching Twilio Super SIM 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.
FAQs
Specific to using Twilio - Supersim API through Jentic.
What authentication does the Twilio - Supersim use?
The Twilio - Supersim 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 retrieve a list of billing periods for a super sim. with the Twilio - Supersim?
Yes. Use the GET /v1/Sims/{SimSid}/BillingPeriods endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Twilio - Supersim?
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 retrieve a list of billing periods for a super sim. through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'retrieve a list of billing periods for a super sim.'. Jentic returns the matching Twilio - Supersim operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Twilio - Supersim have?
The Twilio - Supersim exposes 31 endpoints covering supersimv1billingperiod, supersimv1esimprofile, supersimv1fleet operations.
Can I limit what my agent is allowed to do with the Twilio Super SIM API?
Yes. Jentic One is self-hosted by you, so your own rules decide which Super SIM operations and credentials the agent may use. Because the API puts the SIM, fleet, and eSIM profile Sids in the URL path, such as /v1/Fleets/{Sid}, you can pin the agent to a single fleet or SIM. You also choose which operations it may call, so write actions like updating a fleet via POST /v1/Fleets/{Sid} stay out of reach unless you explicitly allow them.
GET STARTED