Create a Parakeet Managed Inference Job in the web interface
Serve the Parakeet speech-to-text model behind an OpenAI-compatible transcription endpoint from the CosmicAC web interface.
Create a Parakeet Managed Inference Job to serve the speech-to-text model behind an OpenAI-compatible transcription endpoint. The form has six sections, Job type, Basics, Source, Hardware, Notifications, and Review. Click Continue to move to the next section. For a description of every field, see the Parakeet Managed Inference parameters.
Prerequisites
You need the following before you start:
- A running CosmicAC deployment. See Installation.
- Access to the CosmicAC web interface.
Steps
Open the new job form
In the left navigation, click Jobs, then click New Job.
Select the job type
In the What kind of job? section, select Managed Inference, then click Continue.
Enter the basics
In the Basics section, enter a Job name and add at least one tag in Tags. To add a tag, type it, then press Enter.
Click Continue.
Select the model
In the Model to serve section, select nvidia/parakeet-tdt-0.6b-v3. CosmicAC prefills the configuration from the model master stored for that model, in a Parakeet configuration:
- Chunk duration: seconds of audio per chunk. Minimum 10.
- Chunk overlap: seconds of overlap between adjacent chunks. Must be less than the chunk duration. Minimum 5.
- Max file size: maximum upload size in MB. Minimum 1024.
A Parakeet model master stores no runtime image, data type, quantisation, tensor parallel, or reasoning parser, so the form shows none of those fields. CosmicAC supplies the speech-to-text runtime image from the job type.
Name the endpoint
Under Endpoint, enter an Endpoint name. The name must be unique across every Managed Inference Job in the deployment. A failed job keeps its name until you delete the job.
A Parakeet job serves /v1/audio/transcriptions. See Audio transcriptions.
Require an API key
Under API key required, select Require Authorization header, then click Continue. To create an API key that authenticates requests to the endpoint, see Create an API key in the web interface.
The form shows no Instance resources or Environment variables for a Parakeet job.
Select the hardware
In the Hardware section, select a Location first. The GPU list stays empty until you select one.
Select a GPU from the ones available in that location, where each card shows the GPU's VRAM, CPU, and RAM. Set the GPU count, then set the CUDA / driver. Below the count, On one node is the most free GPUs on any single node, and In this region is the total free across the location.
A Parakeet replica always runs on one node, and the form has no Replicas control. To run more than one replica, create the job with the CLI.
Click Continue.
Select the notification events
In the Notifications section, turn on each job lifecycle event you want this job to report. CosmicAC turns all four on by default.
- job.failed: the job transitions to Failed, and the event carries the failure reason.
- job.degraded: healthy replicas drop below the count you set, and the endpoint stays live.
- job.recovered: the job returns to Active from Degraded or Failed.
- job.restart_storm: any replica restarts three times within 10 minutes.
These preferences cover this job alone. An event you turn on here reaches your webhook only if it's also turned on in Settings → Notifications, which also controls the model health and usage window events for the whole deployment. See Set up webhook notifications.
Click Continue.
Review and create the job
In the Review & launch section, check that it reports Ready to create, then click Create job. If it reports issues instead, click Edit on the row that names the problem, fix it, then return to this section.
Open the endpoint
Wait for the job to start running, then click Open endpoint. To send it audio, see Transcribe audio.