API429 / Google

Google Gemini API: text selection and connection

Compare exact Gemini text IDs, verify access with your API429 key, and start with an ordinary text request. Check the required contract for native Google clients, or follow the Nano Banana guide when your application needs image generation.

Models and current API429 rates

These are exact text model IDs for this family. The public catalog and GET /v1/models for your key answer different questions: a published entry does not prove account access. Preserve hyphens, dots and versions exactly.

Model / exact IDAPI429: USD and billing units
Gemini 4 Argongemini-4-argon
$0.030000000000 / 1,000,000 cached input tokens
$0.600000000000 / 1,000,000 input tokens
$3.000000000000 / 1,000,000 output tokens
Gemini 3.8 Flashgemini-3.8-flash
$0.225000000000 / 1,000,000 cache-write input tokens
$0.022500000000 / 1,000,000 cached input tokens
$0.225000000000 / 1,000,000 input tokens
$1.125000000000 / 1,000,000 output tokens
Gemini 3.5 Flash Litegemini-3.5-flash-lite
$0.0900 / 1,000,000 cache-write input tokens
$0.0090 / 1,000,000 cached input tokens
$0.0900 / 1,000,000 input tokens
$0.7500 / 1,000,000 output tokens
Gemini 2.5 Flashgemini-2.5-flash
$0.090000000000 / 1,000,000 cache-write input tokens
$0.090000000000 / 1,000,000 cached input tokens
$0.090000000000 / 1,000,000 input tokens
$0.750000000000 / 1,000,000 output tokens

Catalog data date: . Rates retain their catalog conditions; an absent row does not mean a free request.

Example budget for gemini-3.8-flash: 1,000 requests with 2,000 ordinary input and 500 output tokens each cost approximately $1.012500. This ordinary text token estimate excludes cache, tools, retries and additional fees. It is not a complete bill or evidence of accepted requests.

Family pricing and calculator · Full catalog

Choose Gemini text for a defined task

Compare Gemini candidates on the same extraction, classification or drafting task. Record the expected format, acceptable omissions and handling of uncertain answers before looking at the output. The selected text IDs below do not stand for every Google model or every modality. Check exact spelling in the catalog and in your account’s model list. Model documentation can describe Google’s own capabilities without proving the same parameters, limits or access through an API429 key.

Distinguish ordinary chat from native Google and images

The ordinary Chat Completions example uses messages and an exact Gemini text ID. It is not a native Google GenerateContent SDK example, and changing the base URL does not establish compatibility with every Google SDK method. Verify the specific documented API429 method when a client requires a native Google request format. Image generation has a separate contract and output checks: the Nano Banana API guide owns that detailed workflow. Use its instructions for image parameters and result validation instead of adding image options to this text example.

Validate a small request before expanding the workload

Start with an artificial example that contains no customer secrets. Store the API429 key on your server and keep it out of source control, browser bundles and shared logs. Check the exact identifier in GET /v1/models with that same key before sending a paid request. A public catalog entry describes published inventory; it does not establish access for every account. Preserve punctuation and version numbers exactly, because a similar display name is not evidence that two identifiers are interchangeable.

Measure an accepted result

Use a small evaluation set with explicit acceptance rules. Inspect HTTP status, finish_reason, returned text and actual usage rather than treating a successful status as a complete business outcome. Include empty input, conflicting instructions and responses that stop before completing the task. Your application should decide whether to retry, set a bounded attempt budget and provide a manual review path. A timeout does not establish that a request was unbilled. Repeated attempts and conversation history can change total consumption.

Keep prices and request capabilities separate

The table uses fresh, unambiguous API429 public catalog rates when available. Missing rates are not zero prices. Follow the dedicated pricing guide for billing units and comparisons; manufacturer quotations do not replace your API429 rate. The example here is ordinary text Chat Completions with a short output budget. It does not verify native manufacturer methods, tools, reasoning, vision, streaming event formats or manufacturer context limits through API429. Check the documented contract for each additional feature before relying on it.

Choose your next connection step

  • Nano Banana API workflow

    Use this dedicated guide to check nano banana api workflow before expanding the workload or changing request parameters.

  • Nano Banana pricing

    Use this dedicated guide to check nano banana pricing before expanding the workload or changing request parameters.

  • API429 quickstart

    Use this dedicated guide to check api429 quickstart before expanding the workload or changing request parameters.

First text request: curl, Python, JavaScript

  1. Create a key in your API429 account and add balance by Russian bank card, a business invoice, USDT or TON. A $10 test balance is available for subscribing to the Telegram channel through the bonus bot.
  2. Use the same key to verify gemini-3.8-flash in GET https://gateway.api429.com/v1/models.
  3. Set API429_API_KEY on the server and send a small paid request. The example does not retry automatically.
  4. Inspect HTTP status, finish_reason, text and actual usage. A timeout does not prove that the operation was unbilled.

The example uses only ordinary text Chat Completions with max_tokens=512. It does not verify native manufacturer methods, tools, reasoning, vision or manufacturer limits through API429. Python and JavaScript check key access before generation; check the model list separately for curl.

curl

curl --fail-with-body https://gateway.api429.com/v1/chat/completions \
  -H "Authorization: Bearer $API429_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model":"gemini-3.8-flash","messages":[{"role":"user","content":"Explain the purpose of HTTP 429 in one sentence."}],"max_tokens":512,"stream":false}'

Python 3

import json
import os
import urllib.request

key = os.environ["API429_API_KEY"]
base = "https://gateway.api429.com/v1"
headers = {"Authorization": "Bearer " + key, "Content-Type": "application/json"}
models_request = urllib.request.Request(base + "/models", headers=headers)
with urllib.request.urlopen(models_request, timeout=30) as response:
    available = {item["id"] for item in json.load(response)["data"]}
model = "gemini-3.8-flash"
if model not in available:
    raise ValueError("Model is unavailable to this key")
payload = json.loads("{\"model\":\"gemini-3.8-flash\",\"messages\":[{\"role\":\"user\",\"content\":\"Explain the purpose of HTTP 429 in one sentence.\"}],\"max_tokens\":512,\"stream\":false}")
request = urllib.request.Request(base + "/chat/completions",
    data=json.dumps(payload).encode("utf-8"), headers=headers, method="POST")
with urllib.request.urlopen(request, timeout=60) as response:
    result = json.load(response)
choice = result["choices"][0]
if choice.get("finish_reason") != "stop" or not choice.get("message", {}).get("content"):
    raise ValueError("Incomplete or empty response")
print(choice["message"]["content"])
print(result.get("usage"))

JavaScript: Node.js 18+

const key = process.env.API429_API_KEY;
if (!key) throw new Error("Set API429_API_KEY");
const base = "https://gateway.api429.com/v1";
const headers = { Authorization: "Bearer " + key, "Content-Type": "application/json" };
const model = "gemini-3.8-flash";
const available = await fetch(base + "/models", { headers, signal: AbortSignal.timeout(30000) });
if (!available.ok) throw new Error("Models HTTP " + available.status);
if (!(await available.json()).data.some(item => item.id === model)) throw new Error("Model unavailable to this key");
const response = await fetch(base + "/chat/completions", {
  method: "POST", headers, signal: AbortSignal.timeout(60000),
  body: JSON.stringify({"model":"gemini-3.8-flash","messages":[{"role":"user","content":"Explain the purpose of HTTP 429 in one sentence."}],"max_tokens":512,"stream":false})
});
if (!response.ok) throw new Error("Generation HTTP " + response.status);
const result = await response.json();
const choice = result.choices?.[0];
if (choice?.finish_reason !== "stop" || !choice?.message?.content) throw new Error("Incomplete or empty response");
console.log(choice.message.content);
console.log(result.usage);

These examples do not prove access for your key; verify the exact ID before a paid request. API contract · Configure your client · Questions and support

Payment and a $10 test

  • Russian bank card. Top up your balance in the account.
  • Invoice for companies. Bank transfer with closing documents.
  • USDT and TON. Top up in crypto.

$10 test credit. Subscribe to our Telegram channel through the bot and get $10 on your balance for the first requests. Get $10 in the bot

Frequently asked questions

Does the public catalog prove access for my key?

No. Check the exact model in GET /v1/models with your own API429 key. A published catalog entry does not prove account access or a successful generation.

Does a consumer subscription cover these API calls?

Consumer chat subscriptions and API429 API usage have separate billing. Use the API429 balance and published API rates for requests sent through this service.

Does the text example verify every native feature?

No. It demonstrates the documented ordinary Chat Completions request shape. Native methods, tools, media inputs and effective limits require their own contract checks and focused validation.

How should I compare cost between models?

Compare total consumption for results that pass your acceptance rules. Include input history, output and repeated attempts. Use current API429 rates and the dedicated family pricing guide rather than substituting manufacturer prices.

Sources and editorial review

Manufacturer documentation describes its family and its own API rules. API429 IDs, rates and request contracts require separate catalog and documentation checks. The original source-review date below is retained; English publication does not renew the source review.

Source review: . To connect, create an API429 account and follow the quickstart instructions.

Telegram