slug: telnyx provider: Telnyx 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: 34 edges: - tag: SIM Cards spec_file: telnyx-sim-cards-api-openapi.yml capability_id: BC-2640.20 capability_id_l1: BC-2640 capability_name: SIM & eSIM Lifecycle Management confidence: 0.93 evidence: POST /actions/purchase/esims PurchaseESim Purchase eSIMs; POST /actions/register/sim_cards RegisterSimCards Register SIM cards reason: Direct lifecycle management of physical SIMs and eSIM profiles — purchase, registration, activation codes, enable/disable voice, status (schemas SIMCardStatus, SIMCardActivationCode, SIMCardRegistration). Unambiguously SIM & eSIM lifecycle management. - tag: Number Portout spec_file: telnyx-number-portout-api-openapi.yml capability_id: BC-2640.40 capability_id_l1: BC-2640 capability_name: Number Portability Management confidence: 0.9 evidence: GET /portouts List portout requests; ListPortoutRejections List eligible port-out rejection codes; WebhookPortoutFocDateChanged reason: Explicit outbound number portability workflow — port-out requests, FOC dates, rejection codes, supporting documents. Unambiguously number portability management. - tag: Porting Orders spec_file: telnyx-porting-orders-api-openapi.yml capability_id: BC-2640.40 capability_id_l1: BC-2640 capability_name: Number Portability Management confidence: 0.9 evidence: GET /porting/loa_configurations 'List LOA configurations'; schemas 'PortingOrderActivationStatus', 'PortingPhoneNumber' reason: Full porting order lifecycle including letters of authorisation, porting phone numbers, activation status and porting reports — inbound/outbound number portability management. - tag: Phone Number Porting spec_file: telnyx-phone-number-porting-api-openapi.yml capability_id: BC-2640.40 capability_id_l1: BC-2640 capability_name: Number Portability Management confidence: 0.88 evidence: POST /portability_checks PostPortabilityCheck 'Run a portability check'; schema 'PortabilityCheckDetails' reason: A portability check determines whether numbers can be ported, squarely number portability management. - tag: SIM Card Actions spec_file: telnyx-sim-card-actions-api-openapi.yml capability_id: BC-2640.20 capability_id_l1: BC-2640 capability_name: SIM & eSIM Lifecycle Management confidence: 0.88 evidence: GET /sim_card_actions ListSimCardActions List SIM card actions; schema BulkSIMCardActionDetailed reason: Tracks individual and bulk lifecycle actions performed on IoT SIM cards (schemas SIMCardAction, SIMCardActionsSummary), which is squarely SIM/eSIM lifecycle management for a mobile connectivity provider. - tag: Dynamic Emergency Addresses spec_file: telnyx-dynamic-emergency-addresses-api-openapi.yml capability_id: BC-2700.40 capability_id_l1: BC-2700 capability_name: Emergency Services Management confidence: 0.85 evidence: POST /dynamic_emergency_addresses CreateDynamicEmergencyAddress Create a dynamic emergency address. reason: Registration of dynamic emergency (E911) addresses used for emergency-call location delivery — a telecom regulatory mandate covered by Emergency Services Management. - tag: Dynamic Emergency Endpoints spec_file: telnyx-dynamic-emergency-endpoints-api-openapi.yml capability_id: BC-2700.40 capability_id_l1: BC-2700 capability_name: Emergency Services Management confidence: 0.85 evidence: POST /dynamic_emergency_endpoints CreateDynamicEmergencyEndpoint Create a dynamic emergency endpoint. reason: Manages dynamic emergency endpoints tied to emergency addresses, supporting regulator-mandated emergency-call routing and location delivery. - tag: Fine Tuning spec_file: telnyx-fine-tuning-api-openapi.yml capability_id: BC-610.60 capability_id_l1: BC-610 capability_name: Artificial Intelligence Management confidence: 0.85 evidence: POST /ai/fine_tuning/jobs create_new_finetuningjob Create a fine tuning job; schema FineTuningJob reason: Operations create, list and cancel model fine-tuning jobs — ML model lifecycle / MLOps, which is Artificial Intelligence Management. - tag: Phone Number Block Orders spec_file: telnyx-phone-number-block-orders-api-openapi.yml capability_id: BC-2640.30 capability_id_l1: BC-2640 capability_name: Numbering Resource Management confidence: 0.85 evidence: POST /number_block_orders 'Create a number block order'; schemas NumberBlockOrder, CreateNumberBlockOrderRequest reason: Ordering and retrieving blocks of telephone numbers is acquisition and assignment of telephone numbering resources — numbering resource management (DID provisioning per the vendor description). - tag: Authentication Providers spec_file: telnyx-authentication-providers-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: GET /authentication_providers FindAuthenticationProviders List all SSO authentication providers reason: CRUD over SSO identity providers scoped to an organization_id — federation configuration, which is squarely Identity & Access Management. Could alternatively read as BC-4230.50 Tenant Identity Federation, but the schema (organization_id, settings_url, short_name) is account-level SSO config rather than tenant fleet management, so the cross-industry IAM capability is the safer edge. recovered_from: sweep-20260828T235257Z-edges.json - tag: WireGuard Interfaces spec_file: telnyx-wireguard-interfaces-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.8 evidence: POST /wireguard_interfaces CreateWireguardInterface Create a WireGuard Interface; GET /wireguard_peers/{id}/config Retrieve Wireguard config template for Peer reason: Creating and managing WireGuard VPN interfaces and peers, with region placement, is provisioning of network connectivity infrastructure — IT Infrastructure Management (network/cloud). Operations and schemas (Interface, InterfaceStatus, RegionOut) plainly describe network plumbing rather than security governance. recovered_from: sweep-20260828T235257Z-edges.json - tag: SIM Card Group Actions spec_file: telnyx-sim-card-group-actions-api-openapi.yml capability_id: BC-2640.20 capability_id_l1: BC-2640 capability_name: SIM & eSIM Lifecycle Management confidence: 0.78 evidence: GET /sim_card_group_actions GetSimCardGroupActions List SIM card group actions reason: Status of asynchronous actions applied to groups of SIM cards (schema SIMCardGroupAction) — part of SIM estate lifecycle administration. Slightly lower confidence as the surface is only action-status retrieval. - tag: Managed Accounts spec_file: telnyx-managed-accounts-api-openapi.yml capability_id: BC-4230.10 capability_id_l1: BC-4230 capability_name: Tenant Provisioning & Lifecycle confidence: 0.75 evidence: POST /managed_accounts CreateManagedAccount 'Create a new managed account.'; POST /managed_accounts/{id}/actions/disable 'Disables a managed account' reason: Creation, enable/disable and limit allocation for sub-accounts managed under a parent account is tenant provisioning and lifecycle in a multi-tenant platform. Some overlap with tenant configuration (channel limits), hence 0.75. recovered_from: sweep-20260828T235257Z-edges.json - tag: Mobile Phone Numbers spec_file: telnyx-mobile-phone-numbers-api-openapi.yml capability_id: BC-2640.30 capability_id_l1: BC-2640 capability_name: Numbering Resource Management confidence: 0.75 evidence: GET /v2/mobile_phone_numbers List Mobile Phone Numbers; PATCH /v2/mobile_phone_numbers/{id} Update a Mobile Phone Number reason: CRUD over the operator's mobile number inventory assigned to services — numbering resource stewardship/assignment rather than a technical object. - tag: OTA updates spec_file: telnyx-ota-updates-api-openapi.yml capability_id: BC-2640.20 capability_id_l1: BC-2640 capability_name: SIM & eSIM Lifecycle Management confidence: 0.75 evidence: GET /ota_updates 'List OTA updates'; schemas CompleteOTAUpdate, SimplifiedOTAUpdate, MobileNetworkOperatorPreferencesResponse, wireless_Errors reason: The wireless_* error schemas and mobile-network-operator-preference payloads show these OTA updates are over-the-air updates to IoT SIM/eSIM profiles and their operator preferences, which is SIM & eSIM lifecycle management rather than generic software update distribution. - tag: Phone Number Orders spec_file: telnyx-phone-number-orders-api-openapi.yml capability_id: BC-2640.30 capability_id_l1: BC-2640 capability_name: Numbering Resource Management confidence: 0.75 evidence: POST /number_orders CreateNumberOrder 'Create a number order'; schemas 'NumberOrderPhoneNumber', 'SubNumberOrderRegulatoryRequirement' reason: Operations order and manage acquisition of telephone numbers (DIDs) including regulatory requirements per number — stewardship and assignment of numbering resources. Ordering here is number-resource acquisition rather than a generic sales order. - tag: Phone Number Reservations spec_file: telnyx-phone-number-reservations-api-openapi.yml capability_id: BC-2640.30 capability_id_l1: BC-2640 capability_name: Numbering Resource Management confidence: 0.75 evidence: POST /number_reservations 'Create a number reservation'; schema 'ReservedPhoneNumber' reason: Reserving and extending reservations of telephone numbers is stewardship/assignment of numbering resources. - tag: SIM Card Orders spec_file: telnyx-sim-card-orders-api-openapi.yml capability_id: BC-2640.20 capability_id_l1: BC-2640 capability_name: SIM & eSIM Lifecycle Management confidence: 0.75 evidence: POST /sim_card_orders CreateSimCardOrder Create a SIM card order; schema SIMCardOrderPreview reason: Ordering and shipment of physical SIM cards to the customer — the distribution stage of SIM lifecycle management. Could alternatively be read as generic order capture, hence moderate confidence. - tag: Short Codes spec_file: telnyx-short-codes-api-openapi.yml capability_id: BC-2640.30 capability_id_l1: BC-2640 capability_name: Numbering Resource Management confidence: 0.75 evidence: GET /short_codes ListShortCodes List short codes; RetrieveShortCode; UpdateShortCode; schema ShortCode reason: Short codes are messaging numbering resources allocated to an account and assigned to messaging profiles/services; listing, retrieving and updating them is stewardship and assignment of numbering resources (BC-2640.30). Some residual chance this is read as product/messaging configuration rather than numbering stewardship. - tag: SIM Card Groups spec_file: telnyx-sim-card-groups-api-openapi.yml capability_id: BC-2640.20 capability_id_l1: BC-2640 capability_name: SIM & eSIM Lifecycle Management confidence: 0.72 evidence: POST /sim_card_groups CreateSimCardGroup Create a SIM card group; SetPrivateWirelessGatewayForSimCardGroup reason: Manages logical groupings of SIM cards and their wireless gateway/blocklist policy assignment — administration of the SIM estate, i.e. SIM & eSIM lifecycle management. Some ambiguity because group-to-gateway assignment also touches network configuration. - tag: Virtual Cross Connects spec_file: telnyx-virtual-cross-connects-api-openapi.yml capability_id: BC-600.50 capability_id_l1: BC-600 capability_name: IT Infrastructure Management confidence: 0.72 evidence: POST /virtual_cross_connects CreateVirtualCrossConnect ... GET /virtual_cross_connects_coverage List Virtual Cross Connect Cloud Coverage; schemas Interface, InterfaceStatus, RegionOut reason: Provisioning and management of private network interconnects to cloud regions, including interfaces and coverage — network/cloud infrastructure provisioning, i.e. IT Infrastructure Management. recovered_from: sweep-20260828T235257Z-edges.json - tag: Assistants spec_file: telnyx-assistants-api-openapi.yml capability_id: BC-610.60 capability_id_l1: BC-610 capability_name: Artificial Intelligence Management confidence: 0.7 evidence: POST /ai/assistants create_new_assistant_public_assistants_post Create an assistant ... POST /ai/assistants/tests Create a new assistant test reason: Lifecycle of AI assistants including prompts, external LLM config, test suites and runs — AI/ML model and agent lifecycle management. Schemas such as ExternalLLM and PromptSyncStatus support this. - tag: AutoRechargePreferences spec_file: telnyx-autorechargepreferences-api-openapi.yml capability_id: BC-4250.40 capability_id_l1: BC-4250 capability_name: Payment Collection & Dunning confidence: 0.7 evidence: GET /payment/auto_recharge_prefs GetAutoRechargePrefs List auto recharge preferences reason: Under /payment/, this configures automatic account top-up when balance runs low — payment-method-driven automatic collection for a prepaid usage model, which maps to Payment Collection within subscription billing. Confidence moderated because the surface is only two preference endpoints, not the collection process itself. recovered_from: sweep-20260828T235257Z-edges.json - tag: Billing Groups spec_file: telnyx-billing-groups-api-openapi.yml capability_id: BC-4250.30 capability_id_l1: BC-4250 capability_name: Invoicing & Statement Management confidence: 0.7 evidence: POST /billing_groups CreateBillingGroup Create a billing group reason: Billing groups organise resources for invoicing purposes; schemas include invoice_Error / invoice_Errors, indicating these groups drive invoice segmentation. Maps to Invoicing & Statement Management, though the operations are plain CRUD so confidence is held at 0.7. recovered_from: sweep-20260828T235257Z-edges.json - tag: Bulk Phone Number Operations spec_file: telnyx-bulk-phone-number-operations-api-openapi.yml capability_id: BC-2640.30 capability_id_l1: BC-2640 capability_name: Numbering Resource Management confidence: 0.7 evidence: POST /phone_numbers/jobs/delete_phone_numbers Delete a batch of numbers; POST /phone_numbers/jobs/update_phone_numbers Update a batch of numbers reason: Bulk lifecycle operations over the customer's telephone number holdings (delete/update numbers, emergency settings, CNAM, forwarding) — assignment and maintenance of numbering resources. The 'jobs' framing is batch plumbing but the managed object is clearly the number inventory. - tag: Charges Breakdown spec_file: telnyx-charges-breakdown-api-openapi.yml capability_id: BC-2660.40 capability_id_l1: BC-2660 capability_name: Bill Presentment & Inquiry Management confidence: 0.7 evidence: GET /charges_breakdown GetMonthlyChargesBreakdown Get monthly charges breakdown; schemas MonthlyChargesBreakdownResponse, NumberBreakdownResult, ServiceDetail reason: Exposes the account's monthly telecom charges itemised by service and phone number — i.e. presentment of billed charges to the customer for review/inquiry. L1 telecom billing is solid; the presentment sub-capability is the best fit though it borders on billing operations, hence 0.7. - tag: Charges Summary spec_file: telnyx-charges-summary-api-openapi.yml capability_id: BC-2660.40 capability_id_l1: BC-2660 capability_name: Bill Presentment & Inquiry Management confidence: 0.7 evidence: GET /charges_summary GetMonthlyChargesSummary Get monthly charges summary; schemas MonthlyChargesSummaryResponse, TotalSummary, AdjustmentLine reason: Returns summarised monthly billed amounts including adjustment lines for the customer's telecom account — bill presentment/inquiry over billing output. Sub-capability choice carries some ambiguity versus billing operations. - tag: Customer Service Record spec_file: telnyx-customer-service-record-api-openapi.yml capability_id: BC-2640.40 capability_id_l1: BC-2640 capability_name: Number Portability Management confidence: 0.7 evidence: POST /customer_service_records/phone_number_coverages VerifyPhoneNumberCoverage Verify CSR phone number coverage reason: A Customer Service Record request is the carrier-to-carrier lookup used to validate phone numbers before porting; the coverage-verification and CSR creation operations are the number-portability pre-check flow. Mapped to Number Portability Management; some residual ambiguity because the spec text does not literally say 'porting'. - tag: Embeddings spec_file: telnyx-embeddings-api-openapi.yml capability_id: BC-610.60 capability_id_l1: BC-610 capability_name: Artificial Intelligence Management confidence: 0.7 evidence: POST /ai/embeddings 'Embed documents'; POST /ai/embeddings/similarity-search 'Search for documents'; schema SupportedEmbeddingModels reason: Operations run AI embedding models over document/URL corpora and perform vector similarity search, with model selection and background task status. This is AI/ML capability delivery, mapped to Artificial Intelligence Management; moderate confidence because it is a vendor-provided inference feature rather than an internal model-lifecycle process. recovered_from: sweep-20260828T235257Z-edges.json - tag: Networks spec_file: telnyx-networks-api-openapi.yml capability_id: BC-2600.20 capability_id_l1: BC-2600 capability_name: Network Configuration Management confidence: 0.7 evidence: POST /networks Create a Network; GET /networks/{id}/network_interfaces List all Interfaces for a Network; CreateDefaultGateway reason: Creates and configures private IP networks, default gateways, and interfaces — network element/resource configuration on Telnyx's connectivity platform. Ambiguity between configuration and inventory keeps confidence at 0.7. - tag: OAuth Clients spec_file: telnyx-oauth-clients-api-openapi.yml capability_id: BC-4270.40 capability_id_l1: BC-4270 capability_name: Developer Identity & Credential Management confidence: 0.7 evidence: POST /oauth_clients Create OAuth client; schema OAuthClientCreateRequest reason: Issuance and lifecycle of OAuth client credentials for developers integrating with the platform — developer identity and credential management. Could alternatively be treated as pure auth plumbing. - tag: OAuth Protocol spec_file: telnyx-oauth-protocol-api-openapi.yml capability_id: BC-4270.40 capability_id_l1: BC-4270 capability_name: Developer Identity & Credential Management confidence: 0.7 evidence: POST /oauth/register 'Dynamic client registration'; POST /oauth/token 'OAuth token endpoint'; POST /oauth/introspect 'Token introspection'; schema OAuthDynamicRegistrationRequest reason: Issuance and introspection of OAuth tokens plus dynamic registration of OAuth clients for a developer-facing communications API platform maps to developer identity and credential management, not to any telecom subscriber capability (no subscriber/SIM/network semantics present). - tag: Phone Number Search spec_file: telnyx-phone-number-search-api-openapi.yml capability_id: BC-2640.30 capability_id_l1: BC-2640 capability_name: Numbering Resource Management confidence: 0.7 evidence: GET /available_phone_numbers 'List available phone numbers'; schemas 'AvailablePhoneNumberBlock', 'RegionInformation' reason: Search over available number inventory/blocks by region is part of numbering resource stewardship; it is not a generic search utility since the objects are telephone numbering resources. - tag: Regulatory Requirements spec_file: telnyx-regulatory-requirements-api-openapi.yml capability_id: BC-2700 capability_id_l1: BC-2700 capability_name: Telecom Regulatory Compliance Management confidence: 0.7 evidence: GET /phone_numbers_regulatory_requirements 'Retrieve regulatory requirements for a list of phone numbers'; schema RegulatoryRequirements reason: Exposes the jurisdiction-specific regulatory obligations that must be satisfied to hold/provision phone numbers — telecom-specific regulatory compliance. No L2 fits precisely (not reporting, not USO), so L1 only.