Telnyx TTS Provider

PassAudited by ClawScan on May 12, 2026.

Overview

This appears to be a coherent Telnyx text-to-speech provider, but users should understand it will send TTS text to Telnyx using their Telnyx API key and that the install/package naming is somewhat inconsistent.

This skill is likely safe for its stated purpose if you want Telnyx as your OpenClaw TTS provider. Before installing, verify the exact npm package/repository, understand that synthesized text will be sent to Telnyx, use a carefully managed TELNYX_API_KEY, and avoid custom base URLs unless you trust the proxy.

Findings (4)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Installing and enabling the provider lets OpenClaw use your Telnyx account for speech synthesis.

Why it was flagged

The plugin is designed to use a Telnyx API key, which is account authority and may incur provider usage charges.

Skill content
"providerAuthEnvVars": { "telnyx": [ "TELNYX_API_KEY" ] }
Recommendation

Use a Telnyx key with the least necessary scope if available, monitor usage/billing, and remove the key or disable the provider if you do not want Telnyx used.

What this means

Text that you synthesize may be transmitted to Telnyx for processing.

Why it was flagged

The provider sends text-to-speech content to an external Telnyx service as part of its stated function.

Skill content
Every `/tts` command, voice note, and ClawdTalk voice call will use Telnyx TTS
Recommendation

Avoid sending sensitive or regulated content to TTS unless Telnyx’s data handling terms are acceptable for your use case.

What this means

If a custom proxy is configured, that proxy may see TTS text and possibly authentication material used for the provider connection.

Why it was flagged

The skill supports a custom WebSocket base URL for proxy setups, which could route TTS text and authentication to a user-configured endpoint.

Skill content
"baseUrl": "wss://your-proxy.example.com/v2/text-to-speech"
Recommendation

Only configure a custom base URL to a trusted endpoint you control or explicitly trust.

What this means

A user could accidentally install a different package name than intended if they follow mismatched documentation.

Why it was flagged

The package name differs from the README install command, which references openclaw-telnyx-tts, creating a minor provenance/installation ambiguity.

Skill content
"name": "telnyx-tts-provider"
Recommendation

Confirm the package name, publisher, repository, and OpenClaw plugin manifest before installing.