generated: '2026-07-25'
method: searched
source: >-
  npm registry search (sktelecom, skopenapi), PyPI (sktelecom, skt-openapi, axtts),
  github.com/sktelecom repository listing via the GitHub API, and the SK open API product
  and reference documentation — all probed 2026-07-25.
summary: >-
  SK Telecom ships no first-party client library for any of its own APIs. The SK open API
  reference documents integration exclusively as raw HTTP with an appKey header, illustrated
  with curl/requests snippets generated by ReadMe. The github.com/sktelecom organisation is an
  open-source programme office (SBOM and licence tooling: onot, bomlens, oss-guide,
  compliance-artifacts, sktelecom.github.io) plus a 2025 hackathon repo — no SDKs, no API
  definitions. SDKs advertised on the portal (Android, iOS, JavaScript) belong to TMAP, i.e.
  TMAP Mobility Co., Ltd., a separate company distributing through the same gateway.
packages: []
registries_probed:
- {registry: npm, query: sktelecom, results: 0}
- {registry: npm, query: skopenapi, results: 0}
- {registry: pypi, package: sktelecom, status: 404}
- {registry: pypi, package: skt-openapi, status: 404}
- {registry: pypi, package: axtts, status: 404}
- {registry: github, org: sktelecom, repos: 7, sdks: 0}
related_publishing:
- registry: huggingface
  org: https://huggingface.co/skt
  kind: models, not client libraries
  artifacts: [A.X-K1, A.X-4.0, A.X-4.0-Light, A.X-3.1-Light, KoBERT, KoGPT2, KoBART]
  note: >-
    SK Telecom's sovereign Korean LLM family is published as model weights, not as an API
    client. Only A.X TTS is exposed on the public SK open API portal.
integration_pattern:
  documented: raw HTTPS + appKey header
  examples: >-
    ReadMe-generated snippets on the reference hubs (e.g. the Python requests example on
    https://ax-tts-skopenapi.readme.io/reference/getting-started-with-ax-tts-api).