Text To Speech X402

What is Text To Speech X402?

Text To Speech X402 is an MCP server that converts text to speech audio using Google's TTS engine. It supports 20+ languages, returns base64-encoded MP3 audio, and charges per call via the x402 protocol (USDC on Base L2) — no API key, signup, or rate limits. It is part of the klymax402 marketplace of 100 micropayment APIs for AI agents.

How to use Text To Speech X402?

Add the server URL https://text-to-speech.api.klymax402.com/mcp to your MCP client config (Claude Desktop, Cursor, ElizaOS, etc.). Alternatively, call the HTTP endpoint POST /api/speak with a JSON body containing text and optionally language; an x402‑aware client handles the payment challenge automatically.

Key features of Text To Speech X402

• 20+ languages with configurable language code
• Base64-encoded MP3 audio output
• Google TTS engine, fast and reliable
• Pay-per-call via x402 (USDC on Base L2)
• No API key, no signup, no rate limits
• Max 200 characters per request

Use cases of Text To Speech X402

• Generate audio narration for articles or scripts
• Build voice assistants that speak user‑provided text
• Create audio versions of content for accessibility
• Power language learning apps with spoken examples

FAQ from Text To Speech X402

What payment method does Text To Speech X402 use?

It uses the x402 protocol: an HTTP‑native pay‑per‑call system that charges USDC on Base L2. No signup or API key is required; the client automatically handles the 402 → sign → retry cycle.

Which languages are supported?

The default language is English (en). Supported codes include fr, es, de, it, pt, ja, ko, zh, ar, ru, hi, and many others.

How much does each call cost?

Each invocation of media_text_to_speech costs $0.005 USD (paid in USDC).

What is the maximum text length per request?

The text parameter is limited to 200 characters per request.

What are the runtime or transport requirements?

The server is accessible via HTTP (MCP or raw REST). Any x402‑aware client (e.g., @x402/fetch, x402-agent-tools, ATXP) can handle the payment flow. No external dependencies other than an x402‑compatible wallet on Base L2.