Telecom Subscriber Management

BC-2640 Level 1 Telecommunications 1 providers 5 API surfaces 1 rated strong or better

Subscriber identity, SIM and eSIM lifecycle, numbering, portability, device identity, and authentication and authorisation across mobile and fixed networks.

Telecom Subscriber Management (BC-2640) is a level-1 business capability in the Telecommunications model. The catalog holds 5 API surface(s) from 1 provider(s) that can perform some part of it, 1 of them rated strong or better. Reach is the vendor surface that lands on this capability — it is not a claim about what any particular organisation has deployed.

Where this capability definition comes from. This capability is part of a published business-architecture model that API Evangelist did not author. It is redistributed here under CC-BY-4.0. Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 Changes: Consolidated from 333 per-L1 YAML files into one JSON; English only (upstream i18n/ omitted); descriptions whitespace-normalised. No capability was added, removed, renamed or re-parented. Source repository · NOTICE and third-party framework attributions

Authorities this capability cites

Cited by the capability model itself. These frameworks are referenced, never redistributed, and citing one does not imply its owner endorses this listing.

Sub-capabilities

Subscriber Identity Management BC-2640.10

Lifecycle management of subscriber identifiers and profiles in the subscriber data layer.

1 provider, 1 API surface

SIM & eSIM Lifecycle Management BC-2640.20

Lifecycle management of physical SIM cards and eSIM profiles including personalisation, distribution, swap, and replacement.

no catalog coverage

Numbering Resource Management BC-2640.30

Stewardship of telephone numbering resources granted by regulators and their assignment to services.

1 provider, 4 API surfaces

Number Portability Management BC-2640.40

Inbound and outbound mobile and fixed number portability and maintenance of routing reference data.

no catalog coverage

Device Identity Management BC-2640.50

Registration and control of device identifiers for service eligibility and stolen-device blacklisting.

no catalog coverage

Subscriber Authentication & Authorisation BC-2640.60

Authentication, authorisation, and accounting of subscribers and devices across access technologies.

no catalog coverage

Providers that reach this capability

Ordered by rating band. Reach means a provider publishes an API surface that can perform some part of this capability — it is not a claim that any particular organisation has deployed it.

Exemplar 1 Complete, well-documented, and agent-ready
SignalWireAvailable Phone NumbersIncoming Phone NumbersPhone NumbersShort Codes5 APIs68.9

Workflows that realise this capability

Arazzo workflows whose own sourceDescriptions call APIs that carry this capability. The link is derived, not asserted: each workflow declares x-realizes-capability-ids with the spec and confidence behind it.

This page carries no rating. Capabilities are not rated. A capability is a description of what a business does, not a thing a company publishes, so a Kin Score would have nothing to measure.
The edge table is a Pro feature. This page shows which providers and tags reach Telecom Subscriber Management. The underlying tag → capability edges — each with the quoted fragment of the provider's own OpenAPI that evidences it, a calibrated confidence score, and the contract-provenance gate it passed — are available through the API, along with company-level capability maps. Only edges at confidence ≥ 0.7 with evidence found verbatim in the source contract are published at all.

See plans →  ·  How the edges are graded →