↓
Rivya AI Docs

Rivya credits: costs, expiry and billing

Check signup credits, monthly allowances, pack validity, spending order and task charges. Find out where to confirm payments and credit returns.

Last reviewed on September 8, 2026

Rivya uses one account balance for chat, images, video, audio, tools and API requests. Creating an API key does not create a separate balance. Open /settings/credits to see your available credits, upcoming expirations and transactions.

Where your credits come from

  • Signup: new accounts receive 6 credits, valid for 30 days. Free has no monthly credit allowance. A task that costs more than your balance requires a top-up.

  • Subscription: Basic includes 300 credits per month, Advanced 800, Pro 1800 and Premium 3600. Credits are issued monthly even with annual billing. Each grant expires after 30 days; unused credits do not remain available indefinitely.

  • One-time pack: 500, 1500, 3500 or 7000 credits, valid for 365 days. Free accounts can buy packs without a subscription. Buying a pack does not start a recurring subscription.

Prices and purchase options

All prices below are in US dollars. Monthly / annual subscription prices are Basic $19.90 / $167.90, Advanced $49.90 / $419.90, Pro $99.90 / $839.90 and Premium $199.90 / $1679.90. Annual prices are the yearly payment, not a monthly charge.

One-time packs cost $49.90 for 500 credits, $129.90 for 1500, $259.90 for 3500 and $459.90 for 7000. Check Pricing and Stripe Checkout for the current offer, applicable discounts, taxes and payment methods. Plans and packs compares the two purchase options.

Which credits are spent first

Rivya uses unexpired credits with the earliest expiration date first. Credits with the same expiration date are used in the order they were issued. Credits without an expiration date come after dated credits; expired credits cannot be spent.

For example, subscription credits expiring tomorrow are used before pack credits expiring next year, even if you bought the pack first. Check upcoming expirations before buying more.

What a task costs

Check the displayed credit estimate after selecting the model and settings. Duration, resolution and other supported options can affect the charge; see Quality, duration and aspect ratio. A new submission is a new billable request, including a retry.

Rivya deducts the reserved amount before sending a billable request for processing. If spendable credits are insufficient, the request cannot proceed. Choose settings you can afford or add credits before trying again.

Chat and generation can be settled after processing. When a valid final usage amount is lower than the reservation, the difference is returned. If usage is missing, invalid or above the reservation, the current settlement flow retains the reserved charge pending reconciliation; it does not automatically deduct the excess.

Failed tasks and credit returns

A processing task has not necessarily failed. Check its final status and credit transactions before submitting again. Qualifying failed tasks return reserved credits to your account; a credit return is not a refund to your payment card. See Failed tasks and credit refunds for troubleshooting.

Where to check payments and subscriptions

Use /settings/billing for your plan, subscription status and billing portal. Use /settings/credits for your balance, expiration dates, pack purchases and transactions.

After Stripe Checkout, /payment waits for Rivya's payment confirmation and directs you to the relevant settings page. Payment updates are processed on the server; a closed browser or return-page timeout alone does not prove payment failed. Check your receipt and account before paying again. Follow Payment checkout for missing credits or an unchanged plan, and Pricing FAQ for subscription questions.

Using the same credits through the API

API activity spends the balance of the account that owns the key. Check API credits and API models before automating requests. The API guide and developer page explain integration options; How Rivya credits work discusses planning usage across tasks.