generated: '2026-07-25'
method: generated
source: openapi/*.yml, https://tmtid.com/developers/
note: >-
  Generated by API Evangelist from TMT ID's published OpenAPI documents. Every operationId
  referenced below exists verbatim in the referenced spec. TMT ID publishes no AGENTS.md or
  first-party skill files (searched); it does publish an llms.txt, captured at
  llms/tmt-id-llms.txt.
skills:
- file: tmt-id-verify-number.md
  name: Verify a mobile number with TMT Verify
  api: openapi/tmt-id-verify.yml
  operations: [POST]
- file: tmt-id-sim-swap-check.md
  name: Check for SIM swap and device change with Network Biometrics
  api: openapi/tmt-id-network-biometrics.yml
  operations: [post-network-biometrics]
- file: tmt-id-silent-network-authentication.md
  name: Authenticate a user with silent network authentication
  api: openapi/tmt-id-authenticate.yml
  operations: [getAccessToken, getConfig, authenticateUserWithMNO, authenticateUserWithOtp, validateUserSession]
- file: tmt-id-routing-and-fraud-intelligence.md
  name: Route and screen traffic with Live, Velocity and TeleShield
  api: openapi/tmt-id-velocity.yml
  operations: [GET]
  also_uses:
  - api: openapi/tmt-id-live.yml
    operations: [GET]
  - api: openapi/tmt-id-teleshield.yml
    operations: [POST]
  - api: openapi/tmt-id-score.yml
    operations: [GET]
  note: >-
    Velocity, Live and Score each publish a single operation whose operationId is literally the
    HTTP method (GET); TeleShield's five operations all share the operationId POST. Those are the
    real, published ids — they are not placeholders introduced here.