Gemini iconChat APIActive

gemini API

Access Google Gemini through API in One's OpenAI-compatible chat API. Advanced text generation, reasoning, and conversation capabilities. 5 credits are pre-deducted, then adjusted by token usage.

Real routes1Real endpoint rows linked to this model.
Endpoint models1Live models sharing this endpoint.
Base cost5 credits$0.05 · 1–5 seconds
Endpoint familyChat API/api/v1/chat/completions
Model IDgemini

Use this in the request body model field.

Endpoint/api/v1/chat/completions

The currently implemented BFF route.

Outputtext

Input types: text

AuthBearer API key

Keys are managed by the shared dashboard.

WebhookNot required

This route does not require webhook handling.

Service highlights

Marketplace-style signals backed by the current live route, without copying external SLA, discount, login, or payment claims.

Live production route

This page only shows endpoints implemented under /api/v1. /api/v1/chat/completions

Synchronous response

This model returns directly without creating a media task.

Shared billing system

Top-up, orders, credit balance, and profile continue through the existing shared console.

Managed provider credentials

Your browser only holds an API in One key; provider calls stay server-side.

Call contract

Use these fields to integrate the current live model route.

Base URL
https://apiin.one
Clients call same-origin APIs; the server BFF forwards to the Worker.
Authorization
Authorization: Bearer <API_KEY>
Managed by the existing Dashboard API Keys page.
Model field
gemini
Send this value in the request body model field.
Result path
/api/v1/chat/completions
Chat models return the result directly.
Billing path
/billing/credits
Uses the existing credits, orders, and top-up logic.

Runtime behavior

This model uses the synchronous chat route and returns a response directly.

Client request/api/v1/chat/completionsDirect response
View usage logs

API Console

Switch between real models on this endpoint, choose a live route, and generate request examples from the current catalog payload.

Live model1 live models
Endpoint1 Routes
ProviderGooglehttps://n62.gogloai.com
Current cost5 credits · $0.05~5 credits pre-deduct, pay-per-token
RuntimeDirect responseChat models return the result directly.
Input / outputtext -> textThis model returns directly without creating a media task.
Backend nodenode62Your browser only holds an API in One key; provider calls stay server-side.
Request previewPOST /api/v1/chat/completions
curl --request POST \
  --url https://apiin.one/api/v1/chat/completions \
  --header 'Authorization: Bearer <API_KEY>'
  --header 'Content-Type: application/json' \
  --data-raw '{
  "model": "gemini",
  "messages": [
    {
      "role": "user",
      "content": "Explain quantum computing in simple terms."
    }
  ],
  "stream": false,
  "include_thoughts": true
}'
Result path/api/v1/chat/completions
Open docs

Endpoint decision panel

Evaluate cost, provider coverage, and production integration behavior across live models on this implemented endpoint.

Endpoint models1These models share the same BFF route and switch through the model field.
Provider coverage1Real provider sources currently exposed by this endpoint.
Cost range5 credits$0.05-$0.05 · Based on the current live catalog base credit cost.
Webhook coverage0/1Models on this endpoint that support callback_url.
Current model position1/1

Sorted by base credits from low to high.

Lowest-cost route in this endpointgemini

Google · 5 credits · $0.05

Production patternSynchronous call

Chat models return the result directly.

Live capabilities

These capabilities come from the current model config and backend route. Unreleased APIs are not listed.

OpenAI

OpenAI-compatible /chat/completions format — drop-in replacement

Usage

Usage-based credit accounting after a 5-credit pre-deduction

128K token context window for long documents

128K token context window for long documents

No Google Cloud or Vertex AI setup required

No Google Cloud or Vertex AI setup required

Request format

Clients call same-origin API routes; the server BFF forwards to the matching Worker.

Parameters

messagesarray

Array of message objects with role (user/assistant/system/developer) and content

Required
streamboolean

Enable SSE streaming responses

Optional · Default true
include_thoughtsboolean

Include model reasoning/thinking steps

Optional · Default true
reasoning_effortstring

Reasoning depth: "low" or "high"

Optional · Default high
toolsarray

Tool definitions for function calling (OpenAI-compatible format)

Optional
response_formatobject

Force structured output (e.g. {type: "json_object"})

Optional

Example request

curl -X POST https://apiin.one/api/v1/chat/completions \
  -H "Authorization: Bearer aio_your_api_key" \
  -H "Content-Type: application/json" \
  --data-raw '{
  "model": "gemini",
  "messages": [
    {
      "role": "user",
      "content": "Explain quantum computing in simple terms."
    }
  ],
  "stream": false,
  "include_thoughts": true
}'

Integration flow

These steps use the current live route and shared account system; login, payment, orders, credits, and profile remain shared.

01

Create a shared API key

Create a key in the existing dashboard. Top-up, orders, credit balance, and profile stay in the shared console.

02

Call the real endpoint

Send a request with the endpoint, model id, and parameters shown on this page. /api/v1/chat/completions

03

Poll task status

Chat models return directly without task polling.

Pricing

~5 credits pre-deduct, pay-per-token

Base cost$0.05
Credits5
BillingSuccessful requests

Use cases

These workflows are supported by the current model and backend node.

01

Build AI-powered chatbots and customer support agents

02

Generate and summarize text content at scale

03

Create AI coding assistants and code generation tools

04

Power reasoning and analysis features in your application

FAQ

Is the Gemini API compatible with OpenAI's format?

Yes. API in One uses the standard OpenAI chat/completions format. You can switch from OpenAI to Gemini by changing the base URL and model name — no other code changes needed.

How much does the Gemini API cost?

5 credits are pre-deducted per request, then adjusted based on actual token usage (pay-per-token). Usage and balance are managed through the shared billing console.

Does the Gemini API support streaming?

Yes. Streaming is enabled by default via SSE (Server-Sent Events). Set stream to false for synchronous responses.

What is the maximum context length?

Gemini 3 Flash supports up to 1M tokens of context, suitable for processing long documents and maintaining extended conversations.