Rivya Model Availability Guide
Understand Rivya model availability, provider changes, direct generation, workflow support, fallbacks, credit hints, and production readiness.
Use this guide when a model appears unavailable, does not support the workflow you expected, or needs a fallback path.
Rivya shows models based on current provider access, workflow support, configuration, and product readiness. Start with the model page, then choose a fallback by task instead of by model name alone.
What Availability Means
Availability can mean several things:
- the model appears in the catalog
- the model supports a specific workflow
- required parameters are configured
- provider access is working
- the model is available for the current region or account context
- the workflow is ready for production use
Do not assume that every model supports every modality or input type.
Why Availability Can Change
Models can change because:
- providers update APIs
- pricing or credit assumptions change
- capabilities move between preview and production
- upload or reference support changes
- a workflow needs maintenance
- Rivya updates routing or safeguards
This is normal for AI products that rely on multiple providers.
How To Choose A Fallback
When a model is not the right fit, choose a fallback by task.
Ask:
- Is the job image, video, audio, chat, or tool-based?
- Does it need references?
- Is quality, speed, cost, or control most important?
- Is this a test run or final asset?
- Is there another workflow that solves the same job?
Use Choosing Models in Rivya and Model Fields and Parameters in Rivya for comparison.
Review Model Pages Before Running
Before spending credits, check the model page for:
- supported modes
- inputs
- output type
- quality or duration options
- credit hints
- commercial-use notes where provided
- examples or sample outputs
Model pages should be treated as inventory, not just promotional pages.
Availability Checklist
Before assuming a model can run a production task, check:
- Confirm that the model is visible in the catalog or model page.
- Check whether direct generation is enabled for the workflow.
- Review supported modes, inputs, outputs, and required parameters.
- Compare credit hints before choosing a heavier fallback.
- Check whether another model or Studio surface solves the same job.
The goal is to pick a runnable path, not to wait on a model that does not match the current task.
When To Recheck Availability
Recheck availability when a provider changes access, a workflow moves between preview and production, or a task needs a different input type.
In those cases, review the model page and choose a fallback before preparing final assets.
Related Pages
Rivya Live Features and Product Scope
Check Rivya's live scope across public pages, models, sign-in requirements, Studio execution, audio coverage, and coming-soon boundaries.
Rivya Model Fields and Parameters Guide
Read Rivya model fields for categories, modes, direct generation, credits, references, uploads, quality, duration, aspect ratio, and outputs.