Version dated 16 September 2026. These rules form part of the Cicora Agreement and apply to RIZZ TRADE orders.
1. What is purchased
1.1. The User purchases access to the Cicora software service or prepays for its use. A Subscription pays for a defined period and the limits provided by the plan. API Pay as you go records actual operations separately. Prepaid units and bonuses are not a bank deposit, currency, investment asset, or means of payment.
1.2. An Account may contain different types of accounting: a Subscription limit, a separately topped-up API Balance, purchased additional volume, and a promotional bonus. They must not be treated as interchangeable unless an Order expressly provides for transfer or use of one product to pay for another. Spending rules and available balance are shown for the relevant type of accounting.
1.3. Credits may not be transferred to another User, sold as money, given away outside a provided function, or used to settle with a third-party seller. The possibility of a lawful refund for an unprovided service is governed separately and is not a “wallet withdrawal.”
2. Price and contents of an Order
2.1. The pricing and API catalogue discloses current offers. Before payment, the User sees the product, period, calculation basis, currency, applicable taxes, and final amount. The purchaser may review the Order before confirmation and retain its terms.
2.2. Plus ($20), Pro ($50), 5× ($100), and 20× ($200) subscriptions have the stated monthly prices. The 5× and 20× levels are compared with the Plus ($20) plan, not with money in an Account Balance. No mathematical multiplier is implied for Pro merely from its price relative to another plan.
2.3. For domestic transactions in Uzbekistan, prices and calculations established for them are used in the currency permitted by law. For an international Order, the billing currency and payment amount are agreed before payment. Where conversion occurs, the applicable procedure and final amount are disclosed; independent conversion by the issuing bank is governed by the User’s relationship with that bank.
2.4. The public API catalogue publishes the exact applicable rates, units, and special terms of the selected Model. A rate per million text tokens is not a universal unit for audio, images, video, or reranking. Different modes, quality, duration, context size, cache, tool, or provider may change the calculation; the applicable rate, unit, and condition are available before a request.
3. Measurement of API usage
3.1. Actually performed volume is recorded using the applicable measures: input and output tokens, cached tokens, internal reasoning where billed, images, audio duration, speech characters, video seconds, requests, or other disclosed units. Parameters and units follow the relevant Model rather than only the general function name.
3.2. For a rate per million tokens, the billable quantity is divided by 1,000,000 and multiplied by the relevant rate. For another unit, its published scale is used. The same consumption must not be charged twice as independent components where the price does not provide for separate operations.
3.3. Some catalogue values describe a base, minimum, or Route-dependent price. A dynamic router or a rate calculated from additional parameters does not become free merely because a service field is zero, negative, or absent. The final amount is determined by the disclosed formula of the relevant mode.
3.4. Before execution, the rate and method of calculation are available and, where exact volume is not known in advance, the estimate or spending limit provided by the product. After processing, the actual units, amount, Model, time, and operation identifier are recorded. This information helps match use to an Order and request review of an error.
3.5. Usage volume is measured by Cicora’s technical systems and the participating provider’s systems within the applicable mode. A difference between a User’s text count and a tokenizer may arise from history, system instructions, tools, attachments, and encoding. In a dispute, records related to the operation are considered; a technical log is not conclusive evidence.
3.6. Rounding, a minimum billable volume, and special pricing intervals are disclosed in the card or billing interface before use. New rules do not apply retrospectively to completed operations. The User must not expect an API price to remain unchanged indefinitely for future requests.
4. Reservation, errors, and repeated requests
4.1. Part of the Balance may be reserved temporarily for a request. A reservation limits available balance but is not the final charge. After completion, actual cost is calculated and the unused portion is released; status and adjustments are shown in the history.
4.2. If a request is rejected before chargeable processing begins, its cost is not automatically treated as used. An erroneous charge is reviewed and corrected. Input rejection by a safeguard, a platform failure, absence of a Result, and cancellation by the Customer have different technical circumstances; they must be assessed by the processing actually performed and supplied and by mandatory law.
4.3. A client-connection loss or closing a browser window does not always stop execution that has already begun. In the case of streaming or a partial Result, performed processing may be charged if that rule is disclosed and permitted by law. The Service may not call every undelivered operation successful merely because a provider billed it.
4.4. A new submission by the User after a timeout may be a separate request. An automatic retry or fallback must remain within agreed settings, budget, and data rules. Switching to a materially more expensive mode does not create unlimited authorisation for additional spending.
4.5. For a disputed operation, provide the Account email, request or Order ID, Model, time, and type of error. Do not send all personal Content if an identifier is sufficient for diagnostics. A confirmed error is corrected; a monetary refund, where due, is made under the Refund Rules.
5. Subscription periods and limits
5.1. A monthly Subscription is activated for the period stated in the Order confirmation. Available capabilities, Models, and limits are shown in the product. “More usage” does not mean a defined number of arbitrary responses: requests of different complexity may consume a limit differently.
5.2. Increased levels are compared using a comparable Model, mode, and accounting period. Rate, concurrency, and separate-function limits may apply independently of total volume. Unused period limits are not purchased cash balance; the refresh and carry-over rules are determined by the disclosed plan terms.
5.3. Renewal is available only after separate consent stating the frequency, amount, and cancellation method. Cancellation stops future renewals and preserves access until the end of the current paid period unless another lawful termination occurs. App-store payments use that store’s subscription-management settings.
5.4. Upgrade or downgrade, immediate migration, crediting, and a change of billing date apply only in a disclosed and confirmed scenario. The mere existence of a more expensive plan does not authorise charging its price automatically or recalculating a past period.
6. Top-up and automatic top-up
6.1. Before a top-up, the credited volume, payment amount, currency, rules relevant to the purchase, and any term of use are displayed. Credit is confirmed by the payment provider’s server. A repeated notice or repeated visit to a success page must not create multiple credits for one purchase.
6.2. Automatic top-up is separate authorisation from a Subscription. When enabled, the threshold, amount or formula, selected payment instrument, available limits, and method of disabling it are shown. The User may amend or withdraw authorisation for future operations. An already initiated lawfully authorised operation is considered separately.
6.3. If the Balance is insufficient and automatic top-up is disabled, new paid actions are limited. We must not increase an authorised amount or change the payment instrument without required consent. A notice of insufficient funds is not a new Order.
7. Lifetime of purchased and promotional units
7.1. The lifetime of separately purchased Credits is stated in the terms of the relevant top-up or package before payment. An undisclosed term is not introduced retrospectively. A change to future rules does not cancel previously purchased active volume contrary to agreed terms and mandatory law.
7.2. Promotional Credit is granted under the relevant campaign. Its applicability, restrictions, lifetime, and order of use are disclosed when it is granted. A free bonus does not create a separate claim to receive its nominal value in money and does not replace a monetary refund that is due without the User’s consent.
7.3. If a bonus is linked to a purchase, the consequences of cancelling that purchase are determined by the campaign terms and law. A paid portion that was not actually provided must not be treated as consumed merely because bonus and payment are mixed in the accounting. The history must permit identification of operations relating to the purchase.
7.4. Attempts to sell, exchange, or transfer Credits without authorisation may lead to access restriction and review. Account termination, mandatory refunds, and lawful retention of documents are governed by the agreement; this clause does not create automatic confiscation of every paid balance.
8. Taxes, confirmations, and corporate billing
8.1. Applicable taxes and data needed to determine them are accounted for in the Order. The Customer provides accurate information about country, organisation, and tax status where needed. Having a TIN does not by itself mean tax exemption or the application of reverse charge.
8.2. After payment, an electronic confirmation is provided and can be retained. Mandatory tax and accounting documents are produced under applicable rules. A successful authorisation email is not always the same as a fiscal receipt; these documents must not be substituted for each other.
8.3. Post-payment, a credit limit, an individual invoice, a special payment term, or a corporate commitment to a minimum volume applies only if separately agreed. They do not arise for an ordinary prepaid Account under this page. An invoice error is considered upon a request supported by documents, while preserving legal rights.
8.4. A foreign procurement agreement for a Model, a provider discount, or its non-refundable costs do not automatically change the Cicora terms accepted by the User. Contacts for payment and accounting: support@cicora.ai, +998 90 051 48 40.