Start from Rivya Public Pages

You can browse Rivya before creating an account. When a public page includes a supported form, you can prepare a request there and sign in to run it on the same page. You do not have to visit Studio first. “Public” describes who can open the page, not whether generation is anonymous or free.

Find the right starting page

If you know the output you need, start with Chat, Image, Video or Audio. Use the model catalog when you already have a model in mind or need to compare supported inputs. Check the current availability and form rather than assuming every listed capability can run now.

The tool directory organizes specific tasks. A tool name does not mean it has a separate execution engine or accepts every file type. Read the selected tool’s instructions and model controls; the tools guide explains task presets and their behavior.

Examples help you understand a possible use, but do not guarantee the same output. Choose an example relevant to your task, then adapt the subject, references and settings. For reusable starting points, see prompt templates.

Prepare your request before signing in

Browsing pages and typing into an available form do not submit a generation or consume generation credits. Uploading supported files, sending a chat message and running a generation require sign-in. Availability, valid inputs and sufficient credits are still checked afterward.

Before opening sign-in, copy your unsent text into a local note and record the model and important settings. A return address is not a backup of your draft. Login may reload the page, and not every parameter or query detail is retained. Keep the original files so you can attach them again if needed. See sign-in and saved work.

Signing in does not run the request for you, unlock a paused model or enable a coming-soon tool. If an option cannot be used, check model availability instead of repeating the same click.

Run a first request on a supported form

1. Sign in using the account you want to work in. If necessary, reopen the model or tool page you selected. The account access guide explains the sign-in options.

2. Check the selected model, restore your text and settings, and attach any required files. Wait for uploads to finish and confirm the attachments. File support depends on the current form; see references and uploads.

3. Review the displayed credit estimate and submit once. An estimate is not a universal fixed price; see credits and billing for reservation and settlement.

4. Wait for the result and review it. If the browser disconnects after submission, check History before sending again. A missing response on screen does not prove the task failed.

A page without a supported execution form remains useful for reading, but describing your intended task there does not start it. Follow the available model or workspace link and inspect the destination form.

Use Studio when you need the workspace

Open Studio for the signed-in workspace and ongoing model-based work. Staying on a supported public form is also valid for a first request. Both use your account context; moving between them does not create another credit allowance.

A link into Studio may carry a prompt and a supported reference. It does not transfer a complete project with every setting, attachment and previous result. Confirm the destination model and input before submitting. Opening a category or generic model page is also different from reopening a saved conversation.

Keep the result and choose the next step

Find submitted tasks and saved conversations in History using the original account. To continue a chat, open its saved conversation rather than merely returning to the same model. See saved sessions for what is retained and what must be copied separately.

Save important outputs locally using the download guide. A public example page is not your personal project storage, and saved history does not mean every output remains available indefinitely.

If sign-in, upload or submission keeps failing, use troubleshooting. Keep the relevant page address and task identifier for support, without including verification codes or API keys.