Help, without the guesswork

No. Weighted Avlumo units are a product allowance. Actual input, output and cache tokens are usage measurements. Different tariff categories have different coefficients, so units do not guarantee a fixed number of model tokens.

Each access retains the product and pricing profile sold with it. Published rates and estimates must use that profile and tariff version. Changing language or theme cannot change the allowance, pricing profile or recipient.

Clients and parallel agents can reuse a permitted key. All keys for one access share its native allowance; independently purchased stock keys do not share funds. Model and client compatibility still needs qualification.

Prepared access can be valid for narrow status while inference remains locked. Activation requires verified payment for the exact delivered item. Key possession or first use is not payment, and activation does not grant the base allowance twice.

Use the permitted original purchase route. A new-key product creates independent access; a compatible refill must verify its exact original recipient, product and profile. Allowance and actual sale currency or fees are separate facts. Refunds follow the original permitted route.

First check your original delivery where a copy is available. Exceptional recovery or replacement needs qualified original-order or owner proof; a new purchase is not required. Never paste a key into a support message.

Check activation, model availability, the exact protocol/model ID and service status. Keep a safe request reference and UTC time for support. Do not blindly replay ambiguous paid work or assume a failed/incomplete response cost nothing.

No. Opening an EN/RU URL sets only that document; using the language switch deliberately saves a choice on this device when available. Auto follows supported browser preferences. Language and theme cannot change shared communication settings, financial identity, purchase source or pricing.