Rivya Model Availability: What You Can Run
Understand available, paused and coming-soon models in Rivya, check Studio and API input requirements, and choose a compatible alternative before spending credits.
Last reviewed on September 8, 2026
A model appearing in Rivya's catalog does not mean it can accept a new request. Check the status on its current page, then confirm that its supported mode and inputs match your task. Availability describes Rivya's access to that model; it is not a live health check or a guarantee of output quality.
Read the Model Status
| Status | What it means for a new request |
|---|---|
| Available | The model is enabled for supported requests. Sign-in, input validation and credit requirements still apply. |
| Temporarily unavailable | New requests are disabled. The catalog page may remain visible with an explanation or alternatives. |
| Coming soon | The model is listed for reference but cannot run yet. The label does not promise a launch date. |
studio_only in API metadata | The model is not callable through Public API v1. Do not infer that a working Studio entry exists; check the current page and its actual controls. |
Opening a paused or coming-soon model's Studio URL redirects to its public model page. Buying credits does not turn that model on. A visible description, template or old example is not proof of current access. See Current Features.
Check the Exact Mode and Inputs
An available model may support only some of the operations associated with its name. Before preparing files or sending a request, check:
The output category and supported mode: text, image, video or audio input as documented.
Required references, file count, formats, sizes and any duration or dimension limits.
Offered settings, such as aspect ratio, resolution, duration or voice, and which combinations are accepted.
The credit estimate for those inputs and settings.
Use Model Fields and Parameters, References and Uploads and Credits and Billing. A capability mentioned for a model elsewhere is not automatically implemented in Rivya.
Use the Current Studio Entry
A category shortcut opens an available default model. Check the model selected after opening it; it may differ from a model named in an older tutorial. Choose the required model in Studio and inspect the form before submitting. Refresh a stale page if its controls disagree with the current model page.
ElevenLabs Sound Effect V2 and Audio Isolation are currently paused. Suno Sounds can create new sound sketches, but it cannot clean or isolate an existing recording. If the task is recording repair, that alternative does not meet the same requirement.
Availability changes can reflect access, integration or capability restrictions. Use the explanation on the current model page when provided; do not assume a specific outage, regional restriction or account problem from the status alone.
Check API Availability Separately from Input Support
For an integration, inspect GET /api/v1/models or the model's API reference. A model's appearance in the response does not make it callable. Check api_status, supports_direct_generation, api_input_status and the documented inputs.
An available model may still require the Files API for a reference-based mode. A supported URL parameter is not interchangeable with a file upload, and a text-only example does not demonstrate attachment support. Use the original model-bound upload response, including required metadata, where the reference instructs you to do so. See API Models and API Files.
Each model reference at /docs/api/models/{id} provides its current API fields, input requirements and notices. Use the ID returned by the model listing; do not construct one from the display name or copy another model's parameters.
Choose an Alternative That Solves the Same Task
Compare the required operation first, then input compatibility, controls and estimated credits. A text-to-image model is not necessarily an image editor; a sound generator is not necessarily an audio-cleanup tool. Related models are options to inspect, not interchangeable replacements.
When switching, copy your prompt, retain original files, and check all settings again. Model changes can reset parameters or remove incompatible references. A new submission is a separate request and may cost credits; the previous result is not guaranteed to be reproduced. See Choosing Models and How to Pick the Right Model.
If You Already Submitted a Request
A later availability change does not tell you the outcome of an earlier task or its credit settlement. Check the original generation page and History, then follow Task Lifecycle. Do not treat a missing model option as proof that an existing task was cancelled, refunded or deleted.
If the status and controls remain inconsistent, record the model name, page, approximate time and timezone, and exact message. Include a task or session reference if relevant when contacting [email protected]. Do not send login codes or API keys. Follow Troubleshooting before repeating a request with an unclear outcome.