Home ／ Gemini 3.5 Flash Lite

Where to Purchase Gemini 3.5 Flash Lite API and What It Costs

Gemini 3.5 Flash Lite is listed in the OpenLux pricing panel. Its base rate is $0.30 per 1M input tokens, $2.50 per 1M output tokens, and $0.03 per 1M cache-hit tokens; the billed rate is the base rate multiplied by your assigned group multiplier. Supported payment methods, balance-credit timing, and account review requirements are Not yet measured.

Where can I buy Gemini 3.5 Flash Lite API access?

The available purchase route evidenced here is the OpenLux panel, whose pricing endpoint lists gemini-3.5-flash-lite as an active Google chat model. The panel data was retrieved on August 4, 2026, and the pricing catalog contains 452 models overall. That catalog figure does not establish that only those models are supported, because the published table covers the 150 highest-volume models and omits 302 others.

The supplied data does not document an official Google purchase path for a particular country or account type. It also does not state whether direct official access is available in a given region. Treat official availability as Not yet measured for this page, and verify it in the official console applicable to your organization before choosing a procurement route.

For teams that need a channel decision rather than a model comparison, the practical check is simple: confirm that gemini-3.5-flash-lite appears in the selected panel account, confirm the assigned group, and review the displayed recharge options before committing funds. This page cannot confirm that every account sees the same groups, models, or balance rules.

How much does Gemini 3.5 Flash Lite API cost?

The listed base price for gemini-3.5-flash-lite is $0.30 per 1M input tokens, $2.50 per 1M output tokens, and $0.03 per 1M cache-hit tokens. These are token prices in U.S. dollars, not a flat monthly subscription fee. The final billed amount is base price multiplied by the user group multiplier.

For example, the default group multiplier in the supplied panel data is ×0.07353. At that multiplier, the calculated rates are $0.022059 per 1M input tokens, $0.183825 per 1M output tokens, and $0.0022059 per 1M cache-hit tokens. These calculations are illustrative for the default group only; do not use them for another group without recalculating.

The panel lists several Gemini-related groups with different multipliers, including huawei-gemini at ×0.06618, Aistudio-Gemini-1 at ×0.17647, Aistudio-Gemini-2 at ×0.26471, Aistudio-Gemini-3 at ×0.44118, Aistudio-Gemini-4 at ×0.95589, and Vertex-Gemini-1 at ×0.80883. The data does not specify which group a buyer will receive, so the final rate must be confirmed in the account before purchase.

Which purchase channel, payment method, and credit time should I compare?

Use the panel account as the only evidenced channel in this comparison. Its price basis is published as model base price multiplied by the assigned group multiplier. The payment method is Not yet measured, the time for credited balance to become usable is Not yet measured, and any minimum recharge amount is Not yet measured.

For an official Google route, the price basis, payment method, credit timing, regional eligibility, and review process are all Not yet measured in the supplied facts. This page therefore cannot claim that a card, bank transfer, local wallet, invoice account, or any other payment option is accepted by either route.

Before paying, record four values from the purchase screen: the selected group name, its multiplier, the amount to be credited, and the payment status. Then compare the effective input, output, and cache-hit rates against the base formula. This avoids treating a base rate as the rate that will be charged to your account.

How do I place an order and get a key?

The complete documented purchase flow is Not yet measured because the supplied facts provide pricing data but do not provide account-registration screens, payment instructions, or key-creation steps. It would be inaccurate to invent clicks, identity-review requirements, or balance settlement behavior.

A defensible operational sequence is to create or access the relevant panel account, locate gemini-3.5-flash-lite in that account, identify the group multiplier, select a recharge option shown by the panel, complete the payment flow it presents, and then obtain credentials only through the account’s documented credential-management area. The exact labels, required fields, and issuance timing are Not yet measured.

Do not place a production key in source control, tickets, browser screenshots, or client-side code. This is standard credential handling guidance rather than a claim about a particular provider feature. Store the key in a server-side secret mechanism and rotate it through the provider’s documented workflow if it is exposed.

What is the first runnable request after I receive the key?

A verified runnable request cannot be published from the available facts. The endpoint URL, authentication header name, request schema, API version, and response schema for this purchase route are Not yet measured. Supplying a curl command with invented values would create a configuration that appears actionable but may fail or send credentials to the wrong endpoint.

After the key is issued, use the request example generated or documented within the same account that issued it, and set the model identifier exactly to gemini-3.5-flash-lite. Confirm the endpoint and authentication format from that documentation rather than substituting a request format from another Gemini service or a similarly named model.

For the first call, use a non-sensitive text prompt and inspect the returned usage and billing information if the chosen channel exposes it. The supported request fields, media-input format, token accounting fields, and rate-limit behavior are Not yet measured here, so those details belong in the channel’s current API reference rather than this procurement page.

Are invoices, refunds, and exhausted balance handled automatically?

Invoice availability is Not yet measured. The supplied pricing data does not state whether the panel or any official route provides invoices, what legal entity would issue them, what information is required, or whether invoices can be requested after a recharge. Buyers with accounting requirements should verify this before payment rather than assuming balance purchases are invoiceable.

Refund eligibility, refund method, and processing time are Not yet measured. Since those terms are absent from the supplied facts, a buyer should read the current checkout and service terms before adding a larger balance. Do not assume unused balance is refundable or that a payment reversal will restore the same purchasing conditions.

The behavior when balance is exhausted is also Not yet measured. Monitor balance and usage in the selected account, preserve a small operational buffer based on your own observed traffic, and test the failure behavior before deploying a workflow that depends on continuous calls. Rate limits and any free usage allowance are Not yet measured; this page cannot represent the API as free or promise a particular throughput.

Still stuck? Full documentation and support are at OpenLux.

Get started

Confirm the account group and integration documentation first, then validate Gemini 3.5 Flash Lite with a small request

Start with free credits

Official site: OpenLux official site

Last updated 2026-08-05　|　Written and maintained by OpenLux.
Latency and pricing figures come from our own measurements. Where they differ from the vendor's site, the vendor's live page wins.