VOX Logo
  • Pricing
  • Contact
Log InSign Up
Voxworks Logo

Australian AI Voice Infrastructure

NVIDIA Inception Program

© Copyright 2026 Voxworks® (ABN 14 691 875 153). All Rights Reserved.

Solutions

  • Virtual Receptionist
  • AI Cold Calling
  • Batch Calling

Platform

  • Voice Engine
  • Transcription API
  • Australian Voices
  • Security & Compliance

Industries

  • Real Estate
  • Property Management
  • Car Dealerships
  • Trades
  • Medical
  • Dental
  • Legal

Company

  • About Us
  • Careers
  • Voice Talent
  • Contact

Resources

  • Documentation
  • AI Voice Report
  • Blog
  • FAQs
  • Support

Legal

  • Terms of Service
  • Privacy Policy
Australian Transcription API

Realtime transcription, hosted in Australia.

Voxworks hosts a local Deepgram API endpoint for Australian realtime speech-to-text. Build voice agents, live captions, agent assist, and call analytics without sending every stream through offshore infrastructure.

Join the previewSee endpoint pattern
Path
/v1/listen
Protocol
WebSocket
Launch
Private preview

Local route

Sydney-first speech-to-text path

Map of Australia showing local transcription infrastructure

AU media stream

Caller audio stays on a local network path.

Voxworks STT

Realtime speech recognition patterns.

Your app

Transcript events for actions and analytics.

Why this page exists

Realtime transcription APIs are now infrastructure decisions.

Speech-to-text providers increasingly compete on streaming behavior, model choice, endpoint options, and deployment geography. For Australian voice products, the endpoint location can matter as much as the model.

Deepgram global API

Excellent streaming STT models and mature SDKs. Teams still need to consider endpoint geography for Australian callers.

OpenAI transcription APIs

Strong file and realtime transcription options, but migrations often involve different event schemas and realtime session patterns.

Google, AWS, AssemblyAI

Established speech-to-text APIs with streaming modes, custom model choices, and region or deployment tradeoffs.

Voxworks Australian endpoint

A local path for developers who want Deepgram-powered realtime transcription with Australian hosting and practical migration help.

Endpoint pattern

Use the Voxworks SDK with an Australian endpoint.

The Voxworks SDK is the public integration surface. Under the hood it can preserve familiar Deepgram-compatible streaming semantics while giving developers a Voxworks client, Voxworks auth, and Voxworks event names.

Voxworks SDK configuration

Set region: au, keep your app architecture familiar, and validate supported streaming options during onboarding.

Controlled preview access

We provision keys for real workloads and confirm rate limits, retention expectations, and security requirements first.

Deployment guidance

Use the preview to evaluate latency, transcript shape, reconnect behavior, and production monitoring before launch.

voxworks-transcription.ts
import { VoxworksTranscriptionClient } from '@voxworks/transcription';

const voxworks = new VoxworksTranscriptionClient({
  apiKey: process.env.VOXWORKS_TRANSCRIPTION_KEY,
  region: 'au',
});

const stream = await voxworks.transcription.stream({
  model: 'nova-3',
  language: 'en-AU',
  interimResults: true,
  smartFormat: true,
});

stream.on('transcript', (event) => {
  console.log(event.text, event.isFinal);
});

stream.sendAudio(audioChunk);
Capabilities

Built for developers shipping realtime speech products.

Realtime WebSocket streaming

Stream live call audio, meeting audio, or media frames and receive transcript events while the conversation is still happening.

Built for low-latency voice flows

Designed for voice agents, call analytics, captions, QA monitors, and agent-assist products where transcript delay affects the product experience.

Australian endpoint path

Keep Australian audio workloads close to your users and product systems, with onboarding support for local network and compliance requirements.

Familiar Deepgram patterns

Use familiar model, language, endpointing, interim result, and formatting concepts instead of rewriting your whole transcription stack.

Production integration support

Get help designing reconnect behavior, transcript callbacks, downstream events, and observability for long-running streams.

Australian security posture

Discuss private-preview options for ephemeral processing, retention controls, access management, and enterprise security review.

Use cases

Where a local transcription endpoint helps.

  • AI voice agents that need fast turn detection and live transcript context.
  • Contact centre QA, compliance monitoring, and live agent assist.
  • Meeting, webinar, and event captions for Australian audiences.
  • Telephony analytics pipelines ingesting SIP, Twilio, Telnyx, or WebRTC audio.
  • Call recording transcription where Australian data residency matters.
Migration

Move carefully, with production behavior checked first.

1

Share your current transcription path

Tell us whether you use the Deepgram SDK, raw WebSockets, a telephony media stream, or another transcription API today.

2

Validate compatibility

We confirm models, language settings, formatting options, interim result behavior, timeout handling, and expected concurrency.

3

Test on Australian audio

Run side-by-side tests on local accents, noisy phone calls, real customer vocabulary, and your downstream transcript parser.

4

Move selected traffic

Route pilot traffic to the Australian endpoint, observe latency and transcript quality, then expand as your launch plan matures.

FAQ

Questions teams ask before moving realtime transcription.

Is this an Australian Deepgram API endpoint?

Voxworks is launching an Australian-hosted endpoint for teams that want Deepgram-powered real-time transcription closer to Australian callers and media streams. Contact us for private preview access and endpoint details.

Can I use my existing Deepgram SDK or WebSocket client?

The preview is designed for low-friction migration. Supported clients can point to a Voxworks Australian base URL and use familiar streaming transcription patterns such as /v1/listen, model selection, interim results, and smart formatting where available.

Does it support real-time transcription?

Yes. The first release is focused on real-time streaming transcription for calls, voice agents, live captions, and contact centre monitoring, with interim and final transcript events over WebSocket.

Why use an Australian transcription API endpoint?

A local endpoint can reduce network distance for Australian audio, simplify data residency discussions, and avoid routing every realtime stream through distant regions before your application can act on the transcript.

Is this available now?

Voxworks is preparing a private launch. Teams with Australian realtime transcription workloads can contact us to discuss early access, expected call volumes, security requirements, and migration support.

Private preview

Tell us about your Australian transcription workload.

We work with developer partners with real-time audio workloads, especially voice agents, contact centres, captions, and call intelligence products. Send your use case and we will reply with fit, timeline, and technical next steps.

Realtime traffic

Expected concurrent streams, audio format, and transcript event needs.

Security review

Retention, privacy, access control, and Australian data residency requirements.

Contact Voxworks

Request endpoint access

Mention the Australian Transcription API and include your current transcription provider if you have one.

Include your use case, current call volume, or timeline if you want a more tailored reply.

Related reading

Technical context for teams evaluating realtime voice and transcription infrastructure in Australia.

Voice Engine

How Voxworks handles low-latency voice pipelines for Australian calls.

Data sovereignty for AI voice

Why local hosting and data controls matter for Australian voice products.

Why AI voice is hard

The moving parts behind realtime transcription, reasoning, and speech synthesis.