Venice Voice - 1 million Voice sentences processed in its first 24 hours (+changelog)

Venice Voice
Over the last 24 hours, Venice Voice has processed more than 1 million sentences. We’re thrilled to see the interest in this offering and look forward to including its capabilities via the API in the coming weeks.

Qwen QwQ 32B available for Pro and API users
Today, we enabled Qwen QwQ 32B for all Pro users and API users. Per the Qwen docs, QwQ is the reasoning model of the Qwen series. Compared with conventional instruction-tuned models, QwQ, which is capable of thinking and reasoning, can achieve significantly enhanced performance in downstream tasks, especially hard problems. QwQ-32B is the medium-sized reasoning model, which is capable of achieving competitive performance against state-of-the-art reasoning models, e.g., DeepSeek-R1, o1-mini.

Venice’s QwQ implementation is web enabled and supports structured responses.

This model replaced Deepseek R1 70B as our medium weight reasoning model.

App

  • Generated images now contain EXIF metadata including the generation settings used to create the image. This metadata can be disabled in the Advanced Image Settings.
  • Made numerous updates to Markdown rendering in chat to fix issues with ordered lists and code blocks.
  • Permit WebP images to be uploaded by dragging and dropping them into the chat input.
  • Optimized Venice Voice sentence chunking to ensure invalid characters aren’t sent to the voice model, and to reduce network overhead for longer conversations.

API

  • Using the new format parameter, the API can now generate WebP images. Images currently default to PNG to maintain compatibility with prior generation. This will change in the future, so please add a specific format to your API calls if the response format is important.
  • EXIF Image Metadata can be added or removed from generated images using the new embed_exif_metadata parameter.
  • Reasoning models now expose a supportsReasoning capability in the models list endpoint. The docs have been updated.
  • Fixed a bug where the Rate Limit API would not show default explorer tier limits.
  • Removed the admin key requirement on the Rate Limits and Balances endpoint and the Rate Limit Logs endpoint.
  • Remedied Swagger validation issues in our published swagger docs and added a step to our CI pipeline to ensure future validation.