slug: twilio provider: Twilio generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Telecommunications min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 17 edges: - tag: ESimProfiles spec_file: twilio-esimprofiles-api-openapi.yml capability_id: BC-2640.20 capability_id_l1: BC-2640 capability_name: SIM & eSIM Lifecycle Management confidence: 0.88 evidence: POST /v1/ESimProfiles CreateEsimProfile; schema supersim.v1.esim_profile, esim_profile_enum_status reason: The surface creates and tracks the status of eSIM profiles for Twilio's Super SIM IoT connectivity — directly SIM & eSIM lifecycle management. - tag: Keys spec_file: twilio-keys-api-openapi.yml capability_id: BC-4270.40 capability_id_l1: BC-4270 capability_name: Developer Identity & Credential Management confidence: 0.85 evidence: POST /Accounts/{AccountSid}/Keys.json createKey Twilio Create an Api Key reason: CRUD over API keys issued to developers for authenticating against Twilio's public APIs — developer credential issuance and stewardship. recovered_from: sweep-20260828T235257Z-edges.json - tag: Sims spec_file: twilio-sims-api-openapi.yml capability_id: BC-2640.20 capability_id_l1: BC-2640 capability_name: SIM & eSIM Lifecycle Management confidence: 0.85 evidence: POST /v1/Sims CreateSim; POST /v1/Sims/{Sid} UpdateSim; sim_enum_status; supersim.v1.sim; wireless.v1.sim reason: Full create/activate/update/delete lifecycle of SIM records with status transitions plus data sessions and usage records — SIM lifecycle management for cellular connectivity. - tag: Channels spec_file: twilio-channels-api-openapi.yml capability_id: BC-430.30 capability_id_l1: BC-430 capability_name: Contact Centre Operations Management confidence: 0.8 evidence: '"Programmable digital engagement center API for building customized omnichannel contact center solutions"; createChannel Twilio Create a Flex Channel' reason: Flex channels configure the omnichannel contact-centre engagement surface (voice, SMS, chat, WhatsApp), which is contact centre operations. Some ambiguity only over whether it belongs under inquiry management versus contact-centre operations. - tag: Auth Tokens spec_file: twilio-auth-tokens-api-openapi.yml capability_id: BC-4270.40 capability_id_l1: BC-4270 capability_name: Developer Identity & Credential Management confidence: 0.78 evidence: createSecondaryAuthToken Twilio Create a Secondary Auth Token; promoteAuthToken Twilio Promote Secondary Auth Token reason: Lifecycle of API auth credentials for the developer account — Developer Identity & Credential Management. recovered_from: sweep-20260828T235257Z-edges.json - tag: Flex Flows spec_file: twilio-flex-flows-api-openapi.yml capability_id: BC-430.30 capability_id_l1: BC-430 capability_name: Contact Centre Operations Management confidence: 0.75 evidence: 'POST /FlexFlows createFlexFlow; description: ''Programmable digital engagement center API for building customized omnichannel contact center solutions ... channels, flows, interactions''' reason: Flex Flows configure how inbound channel messages are routed into the contact centre — contact centre operations configuration. - tag: RatePlans spec_file: twilio-rate-plans-api-openapi.yml reanchored_from: twilio-rateplans-api-openapi.yml capability_id: BC-2650.20 capability_id_l1: BC-2650 capability_name: Tariff & Plan Management confidence: 0.75 evidence: 'POST /v1/RatePlans CreateRatePlan ... schemas: wireless.v1.rate_plan' reason: Wireless rate plans define the data/messaging/voice allowances and roaming terms attached to SIMs — i.e. definition and lifecycle of tariffs and plans underpinning a telecom offer. - tag: Subscriptions spec_file: twilio-subscriptions-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.75 evidence: POST /v1/Subscriptions CreateSubscription; POST /v1/Subscriptions/{SubscriptionSid}/SubscribedEvents CreateSubscribedEvent; schema events.v1.subscription.subscribed_event reason: 'These are Twilio Event Streams subscriptions: consumers subscribe to platform event types for outbound delivery. That maps to lifecycle management of outbound event/webhook subscriptions and event schemas in the developer platform capability. Some residual doubt whether the grader treats this as pure plumbing.' - tag: Workspaces spec_file: twilio-workspaces-api-openapi.yml capability_id: BC-430.30 capability_id_l1: BC-430 capability_name: Contact Centre Operations Management confidence: 0.75 evidence: taskrouter.v1.workspace.task_queue, taskrouter.v1.workspace.worker.worker_statistics, worker_reservation_enum_status, CreateActivity/CreateTask under /v1/Workspaces/{WorkspaceSid} reason: 'This is Twilio TaskRouter: workspaces containing workers, worker activities (availability states), tasks, task queues, workflows and reservation statistics — the routing and workforce-state engine of a contact centre. Maps to contact centre operations rather than any generic workspace/collaboration notion. Not full confidence because a case could be made for inquiry routing (BC-430.10).' recovered_from: sweep-20260828T235257Z-edges.json - tag: Factors spec_file: twilio-factors-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.72 evidence: POST /Services/{ServiceSid}/Entities/{Identity}/Factors createFactor 'Twilio Create a Factor'; 'two-factor authentication API ... Supports TOTP, push authentication' reason: Creating and listing authentication factors for an identity is multi-factor authentication enrolment — Identity & Access Management. Not telecom subscriber authentication, since these are application end users, not network subscribers. - tag: Interactions spec_file: twilio-interactions-api-openapi.yml capability_id: BC-430.30 capability_id_l1: BC-430 capability_name: Contact Centre Operations Management confidence: 0.72 evidence: POST /Interactions createInteraction; listInteractionChannels; 'omnichannel contact center solutions ... across voice, SMS, chat, WhatsApp' reason: Creates and manages customer interactions and their channels in a contact-centre product — contact centre operations. Could alternatively be inquiry handling, hence 0.72. - tag: Secrets spec_file: twilio-secrets-api-openapi.yml capability_id: BC-4210.60 capability_id_l1: BC-4210 capability_name: Configuration & Secrets Management confidence: 0.72 evidence: POST /v1/Secrets CreateAccountSecret; schemas microvisor.v1.account_secret, UpdateAccountSecretRequest reason: Full lifecycle (list/create/fetch/update/delete) of named account secrets keyed by {Key} for the Microvisor runtime, which is squarely runtime Configuration & Secrets Management. Not 0.9 because these are secrets consumed by the customer's IoT devices rather than the vendor's own deployment pipeline. recovered_from: sweep-20260828T235257Z-edges.json - tag: Accounts spec_file: twilio-accounts-api-openapi.yml capability_id: BC-4230.10 capability_id_l1: BC-4230 capability_name: Tenant Provisioning & Lifecycle confidence: 0.7 evidence: POST /Accounts.json createAccount — 'Twilio Create a Subaccount'; 'Twilio Update an Account'; schema 'AccountList' reason: Creation, listing, retrieval and status update of Twilio accounts and subaccounts on the multi-tenant platform — tenant provisioning and lifecycle. Not general customer data management, since the object is the platform tenant/account container itself. recovered_from: sweep-20260828T235257Z-edges.json - tag: HostedNumber spec_file: twilio-hostednumber-api-openapi.yml capability_id: BC-2640 capability_id_l1: BC-2640 capability_name: Telecom Subscriber Management confidence: 0.7 evidence: CreateHostedNumberOrder, ListAuthorizationDocument, schema numbers.v2.hosted_number_order reason: Operations manage orders to host existing telephone numbers on the platform together with signed authorization documents (letters of authority) — telecom numbering/subscriber-number stewardship. Sits in BC-2640 Telecom Subscriber Management; evidence does not cleanly distinguish numbering-resource assignment from portability, so no L2. - tag: Queues spec_file: twilio-queues-api-openapi.yml capability_id: BC-430.30 capability_id_l1: BC-430 capability_name: Contact Centre Operations Management confidence: 0.7 evidence: POST /Accounts/{AccountSid}/Queues.json createQueue Twilio Create a Call Queue reason: Creating and managing call queues for inbound/outbound voice is telephony queueing infrastructure used to run contact-centre operations; mapped to Contact Centre Operations Management with moderate confidence since it is a raw telephony primitive. - tag: RegulatoryCompliance spec_file: twilio-regulatorycompliance-api-openapi.yml capability_id: BC-2700 capability_id_l1: BC-2700 capability_name: Telecom Regulatory Compliance Management confidence: 0.7 evidence: POST /v2/RegulatoryCompliance/Bundles CreateBundle ... numbers.v2.regulatory_compliance.supporting_document reason: Bundles, end users and supporting documents are the evidence packages required to satisfy per-country regulatory requirements for telephone number provisioning — telecom-specific regulatory compliance, though none of the listed L2s (USO, lawful intercept, retention) matches precisely. - tag: Short Codes spec_file: twilio-short-codes-api-openapi.yml capability_id: BC-2640.30 capability_id_l1: BC-2640 capability_name: Numbering Resource Management confidence: 0.7 evidence: POST /Services/{ServiceSid}/ShortCodes addShortCode 'Twilio Add a Short Code to a Messaging Service' reason: Short codes are regulator/registry-allocated messaging numbering resources; the operations list and assign them to a messaging service, matching numbering resource stewardship and assignment to services.