Rivya glossary: credits, models and task states

Use this page to look up a term you see in Rivya's interface, pricing or guides. Product names such as Studio and model names keep their original spelling; explanations describe how they work in Rivya.

Pages and saved work

• Public pages: pages you can browse before signing in, including model introductions, tools, pricing, blog posts and documentation. Browsing a page does not submit a paid request.

• Public start page: a page where you can read about a workflow and prepare a request. Submitting requires sign-in. See public and signed-in workflows.

• Studio: the signed-in work area for chat, images, video and audio. It is not a promise that every unsent draft or setting is saved. See Studio.

• Dashboard: an account overview with your balance and a limited selection of recent work, rather than your complete history.

• History: saved conversations and generation records. Chat has its own history; images, video and audio appear in generation history. A task record does not guarantee its output file will remain downloadable. See History.

• Notifications Center: account and task events, such as payment updates or generation outcomes. An event is not a substitute for the task's current status or your billing records.

• Settings: account-management pages. /settings/billing shows subscription information; /settings/credits shows credit balances and transactions.

Credits and charges

• Credits / wallet balance: the units you can spend through your Rivya account. Chat, generation, tools and API activity use the same account balance. Credits are not a separate cash balance.

• Signup credits: a one-time starter grant for a new account, with an expiration date. It is not a recurring monthly allowance on the Free plan.

• Subscription credits: credits issued monthly with a paid subscription. Annual billing does not mean the entire year's credits arrive at once.

• Credit pack: a one-time credit purchase with its own validity period. Buying a pack does not start a recurring subscription.

• Spending order: unexpired credits with the earliest expiration date are used first. For equal expiration dates, earlier grants are used first. Credits without an expiration date come after dated credits. “FIFO” alone is therefore not an accurate description of which credits Rivya spends first. See credits and billing.

• Credit estimate / credits hint: an indication of cost. Check the estimate after choosing the model and settings; a general model-page hint is not a final charge.

• Reserved credits: credits deducted before a billable request is sent for processing. Settlement reconciles that reservation with valid final usage; unused reserved credits can be returned.

• Credit return: credits added back to the Rivya balance, for example after a qualifying failure or unused reservation. It is not a refund to your payment card, and a partial return can occur on a successful task. See failed tasks and credit returns.

Models, tools and inputs

• Model: the AI system selected for a supported task. Capabilities and input requirements vary by model, even within one category.

• Model page: a public introduction to a catalog entry. It may describe a model that is not currently runnable in Rivya.

• Availability / direct generation: whether a particular model can currently run through the relevant Rivya workflow. Being listed and being enabled are different. See model availability.

• Tool: a focused entry into a chat task, such as preparing a particular kind of text. It uses the selected chat model and account credits; it is not a separate subscription. See tools.

• Prompt: the instruction or description you give a model. In text-to-speech, the text field generally contains the words to speak, so extra instructions may be spoken too.

• Reference / upload: a file supplied to a workflow that accepts it. A reference guides a result; other supported inputs may be transformed or analyzed. The selected model determines file type, count, size and any duration or dimension limits. Uploading a file does not mean every model can use it. See references and uploads.

• Parameter: a supported setting such as duration, aspect ratio or resolution. A setting on one model may not exist on another. See model fields and parameters.

Tasks and results

• Task / generation request: a submitted request to create an image, video or audio result. Submitting again creates another request that may incur another charge, even with the same prompt.

• Task lifecycle: the stages from checking inputs and handling credits to processing and recording an outcome. See the task lifecycle.

• WAITING: the task is waiting; this is not a final outcome.

• GENERATING: processing is in progress. A long wait alone does not establish failure.

• SUCCESS: the task has a recorded successful outcome. This does not guarantee the content meets your brief or that the file remains accessible forever.

• FAILED: a recorded failure. Read the error and credit transactions before trying again.

• Callback / polling: ways Rivya receives or checks a provider's task result. You do not need to inspect these mechanisms to ask for help.

• Output: the generated response or file. Saving a task record and saving a local copy of its file are different actions. See downloading outputs.

Providers, rights and private information

• Provider: an external service used for functions such as generation, payments, sign-in, storage or email. Upstream provider refers to a service involved in processing the request behind Rivya's interface; it is not an additional workspace you must open.

• Commercial use: using a result in a business context, such as a client project, advertisement or product asset. The label alone does not confirm that a particular result is cleared for that use.

• Output ownership: the allocation of output rights described in Rivya's Terms of Service. Read the terms and relevant provider conditions; this glossary does not grant additional rights or guarantee uniqueness or freedom from third-party claims.

• Sensitive data: personal, confidential or otherwise sensitive information in prompts and files. Consider what you submit and which service processes it; see data and provider processing.

If a term is clear but the action still fails, use troubleshooting to find the relevant record and the information to send support.