Cicada TTS

cicada-tts is presented as an audio model from 蝉镜. This profile confirms the public route and published price; validate voices, formats, and limits in your endpoint contract before launching.

cicada-tts is exposed by NexoRouter under the verified 蝉镜 catalog mapping below. This is the delivery contract customers should use, not a promise of additional upstream routes.

Provider names describe the reviewed catalog mapping. NexoRouter does not claim multi-provider failover for a model unless it is measured and published separately.

Public usage pricing for this model ID. The unit changes by endpoint: not every model is billed by tokens.

Input / generation

$0.00 / second

Cached input

—

Output

Pending review

Prices are published after commercial review. A supplier update creates a review; it never exposes supplier discounts, orders, or internal costs.

Performance metrics are published only after NexoRouter has enough model-specific production observations and a defined measurement window.

No benchmark or chart is synthesized from another provider. These fields will populate only from NexoRouter measurements with a sample size and time window.

Privacy-preserving, aggregate model activity from NexoRouter gateway logs. No prompts, API keys, user identities, or IP addresses are exposed.

Success rate is computed from NexoRouter gateway outcomes for this model ID. It is not an upstream SLA, quality score, or benchmark.

NexoRouter exposes this model through /v1/chat/completions. Use a NexoRouter API key and retain the OpenAI-compatible base URL.

curl --fail-with-body 'https://api.nexorouter.com/v1/chat/completions' \
  -H "Authorization: Bearer $NEXOROUTER_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "model": "cicada-tts",
  "messages": [
    {
      "role": "user",
      "content": "Hello"
    }
  ]
}'

Chat Completions example using the exact model ID. Adjust messages and parameters for your use case.

Every profile combines NexoRouter operating data with provider documentation links. A provider link does not become a capability promise until that claim is reviewed and published.

• NexoRouter catalogNexoRouter published catalog
  Aug 27, 2026, 12:52 AM

Update policy: route evidence targets a 6 h cadence and official-document monitoring, when enabled in production, at least every 24 h. A change creates an internal proposal; claims and translations require human review and are revalidated within 30 days.