GPT88 / API Docs
ChatGoogleFeatured1 vendors

gemini-3.8-flash

Featured Google Flash route for low-latency interaction, multimodal understanding, and high-frequency agent subtasks.

Get API Key on gpt88.ccQuickstart

Overview

  • Gemini 3.8 Flash is represented in the current GPT88 featured catalog as a Google Flash route for responsive, high-frequency, and multimodal workflows.
  • It can serve as a fast routing layer for intent detection, extraction, tool selection, content triage, and intermediate agent steps while harder work escalates to a stronger model.
  • The Flash label is catalog positioning rather than a fixed latency or cost guarantee. Measure it with your prompts, concurrency, payload sizes, and selected route.

Best Use Cases

  • Build interactive assistants where first-token and end-to-end latency matter
  • Evaluate image Q&A, multimodal extraction, and visual content triage
  • Handle intent detection, tool selection, field extraction, and result formatting inside an agent workflow
  • Process frequent, short-context, and cost-sensitive requests

Integration Notes

  • Use the GPT88 Base URL https://api.gpt88.cc and set model to gemini-3.8-flash in OpenAI-compatible requests.
  • Call GET /v1/models, then send a minimal POST /v1/chat/completions request to confirm access for the current API key.
  • Start multimodal testing with text or one image, then add multi-turn context, tools, and streaming separately so format errors remain diagnosable.
  • Use it as a fast routing layer and keep an escalation path to a Pro or other higher-capability model for long, difficult reasoning.

Usage Notes

  • Availability, pricing, context limits, rate limits, routes, vision support, and tool support are determined by the current GPT88 console configuration.
  • Flash positioning does not guarantee low latency for every request; image size, context length, tool count, and upstream load affect response time.
  • Test multimodal and structured-output behavior independently instead of inferring all features from a successful text-only request.
  • Before rollout, record success rate, time to first token, end-to-end latency, retries, and usage, and keep a quality-focused fallback route.

Capabilities

Low-latency positioningMultimodal understandingStructured outputTool use

Recommended Scenarios

  • Real-time assistants
  • Image Q&A
  • Information extraction
  • Agent subtasks

Endpoint Path

POSThttps://api.gpt88.cc/v1/chat/completions

The endpoint path is determined by the model category. Chat, image, video, and audio models use different endpoints.

Send requests with Authorization: Bearer <API_KEY>. See Chat Completions API for the full parameter reference.

API Docs

Endpoint
POST /v1/chat/completions
Model ID
gemini-3.8-flash
Content-Type
application/json
Protocol
OpenAI-compatible chat completions endpoint with streaming and non-streaming output.
Base URL
Use https://api.gpt88.cc for OpenAI-compatible and Claude-style tools.

Headers / Auth

  • AuthorizationstringRequired
    Send Bearer <GPT88_API_KEY>. Create the API key in the gpt88.cc console.
  • Content-TypestringRequired
    Request body format. Audio transcription uploads use multipart/form-data.
    Default:application/json
  • Acceptstring
    Non-streaming requests return JSON; streaming chat requests return SSE chunks.
    Default:application/json or text/event-stream

Chat Protocol Differences

For chat models, the protocol used by the client matters as much as the model name. Claude Code / Anthropic SDK and OpenAI SDK build different request paths.

OpenAI CompatibleRecommended
Base URL
https://api.gpt88.cc
Endpoint
POST /v1/chat/completions
Body
{ "model": "gemini-3.8-flash", "messages": [...] }
Anthropic / Claude
Base URL
https://api.gpt88.cc
Endpoint
POST /v1/messages
Body
{ "model": "gemini-3.8-flash", "messages": [...] }

This model is usually best accessed through the OpenAI-compatible protocol. Only use the Anthropic-style path when the target tool explicitly requires it.

Request Parameters

The fields below are generated by model category. Pricing, context limits, rate limits, and available routes should be confirmed in the gpt88.cc console.

  • modelstringRequired
    Current model ID: gemini-3.8-flash. Preserve the exact casing when copying.
  • messagesarray<Message>Required
    Conversation history. Each message includes role and content.
  • streamboolean
    Enable SSE streaming. Useful for chat interfaces and long responses.
    Default:false
  • temperaturenumber
    Sampling temperature. Higher values produce more variation; production workloads usually start with a fixed value.
    Default:1
  • max_tokensinteger
    Maximum output tokens for this request. Real context limits should be confirmed in the console.
  • response_formatobject
    Structured output config, for example { "type": "json_object" }.
  • toolsarray<Tool>
    Function-calling tool definitions. Availability depends on the model and account configuration.

Response Fields

Response bodies generally follow OpenAI-compatible shapes. Media models may return async task IDs or resource URLs.

  • idstringRequired
    Unique completion ID for tracing and debugging.
  • objectstringRequired
    Usually chat.completion or a streaming chunk type.
  • modelstringRequired
    Actual model ID that handled inference.
  • choicesarray<Choice>Required
    Generated choices including message, delta, and finish_reason.
  • usageobject
    Token usage statistics. Streaming calls may return this only at the end or in non-streaming mode.

Status Codes

  • 200OKRequired
    Request succeeded. See the response field table above for the response body shape.
  • 400Bad Request
    Invalid request fields, such as missing required fields, unsupported image size format, or unsupported file type.
  • 401Unauthorized
    API key is missing, invalid, or malformed.
  • 404Not Found
    Endpoint or model not found. Confirm the path is /v1/chat/completions and the model ID is gemini-3.8-flash.
  • 429Rate Limited
    Rate limit, concurrency cap, or insufficient balance. Check the console for the current allowance.
  • 5xxUpstream Error
    Upstream or request failure. Retry with the same Base URL and keep the request ID for debugging.

Errors and Troubleshooting

  • 401: verify Authorization is Bearer <API_KEY> and the key is still valid.
  • 404: confirm the endpoint is /v1/chat/completions and the model ID gemini-3.8-flash is available in the console.
  • 429: reduce concurrency, shorten requests, or check balance and quota in the console.
  • 5xx: retry with the same Base URL and keep the request ID for debugging.

Request Examples

curl https://api.gpt88.cc/v1/chat/completions \
  -H "Authorization: Bearer $GPT88_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "gemini-3.8-flash",
    "messages": [
      {"role": "user", "content": "Introduce gpt88.cc in one sentence."}
    ]
  }'

Expected response (trimmed example):

200 OKjson
{
  "id": "chatcmpl-gemini-3",
  "object": "chat.completion",
  "created": 1730000000,
  "model": "gemini-3.8-flash",
  "choices": [
    {
      "index": 0,
      "finish_reason": "stop",
      "message": { "role": "assistant", "content": "..." }
    }
  ],
  "usage": { "prompt_tokens": 24, "completion_tokens": 64, "total_tokens": 88 }
}