Rivya AI Docs

Rivya AI Help Center

Start with Rivya AI docs for live features, setup, workflows, model paths, tools, credits, billing, uploads, and release checks.

Last reviewed on 2026/04/21

Rivya Docs is the help center for current-product questions that are easy to misunderstand in a multimodal AI workspace:

  • what is actually live today
  • how to start a real task from a public page or signed-in Studio
  • how models, tools, uploads, credits, plans, and packs behave
  • what to review before publishing, paying, or sharing sensitive inputs

Use docs for product rules, setup, billing, and workflow boundaries. Use the blog for narrower comparison and recommendation pages. Use AI Models and Tools when you already want a specific model or tool page.

Start Here: Setup And Live Features

If You Need The Product Shape

If You Are Building With The API

  • Rivya Public API: the developer-facing overview for API keys, model calls, credits, status polling, and limits
  • API Quickstart: the fastest path from key setup to a submitted generation and status check
  • API Model Reference: model-level request fields, defaults, reference media rules, and examples for API-available models
  • Developers: the public developer hub with an online debugger and links back to API key setup

If You Are Deciding What To Buy

If You Are Running Real Work

If You Need Trust, Terms, Or Policy

Shared Vocabulary

  • Rivya Glossary: the shared terms page for Studio, start pages, credits, packs, references, task states, providers, and other recurring terms
  • use it when you are reading both English and Chinese docs and want the concepts to stay aligned without forcing the writing to sound translated
  • keep in mind that Studio stays in English in the docs because it is a product label, path name, and UI concept, not just a generic noun

When To Leave Docs And Read Blog

Choose Your Next Step

Start here to narrow what you should read or do next:

The goal is to leave the help center with a clearer next action, not just a definition.

When To Recheck The Next Step

Recheck before continuing if the current state, required input, cost, access, or approval requirement is unclear.

In those cases, repeating the same action usually makes the issue harder to debug. Confirm the relevant product page, account state, task record, or policy page before continuing.

Table of Contents