GPT88 Agent Docs
ChatOpenAIFeatured1 vendors

gpt-5.6-terra

Balanced tier in the GPT-5.6 preview family for production assistants, SaaS integrations, and routine agent workflows.

Get API Key on gpt88.ccQuickstart

Overview

  • GPT-5.6 Terra is the balanced tier in the GPT-5.6 preview family represented in the current GPT88 catalog.
  • Its positioning favors routine product integration, SaaS assistants, internal workflows, and multi-turn conversations rather than using the highest tier for every request.
  • Actual parameter support, model access, latency, and usage charges remain dynamic and should be verified in the GPT88 console.

Best Use Cases

  • Use it when a lightweight model is not strong enough but the highest tier is unnecessary for every request
  • Evaluate it for OpenAI-compatible SDKs, tool calls, structured output, and streaming in normal business workflows
  • Consider it as a default candidate for support, knowledge-base, content, and internal-assistant applications
  • Use a representative evaluation set when comparing it with GPT-5.5, GPT-5.4, Sol, or Luna

Integration Notes

  • Use the GPT88 Base URL https://api.gpt88.cc and set model to gpt-5.6-terra in OpenAI-compatible requests.
  • A practical routing design is Terra for the default path, Sol for difficult escalations, and Luna for frequent lightweight work.
  • Cursor, OpenCode, Codex CLI, ChatBox, and internal services can use the same OpenAI-compatible configuration while changing only the model ID.
  • Call GET /v1/models before rollout and record quality, latency, errors, and usage against a fixed evaluation set.

Usage Notes

  • Availability, pricing, context limits, rate limits, routes, and feature support are determined by the current GPT88 console configuration.
  • GPT-5.6 Terra is a preview model. Supported behavior and parameters may change, so introduce it through a monitored canary or staged rollout.
  • Do not route requests from the model name alone; account for task complexity, failure cost, latency targets, and budget.
  • If tool calls or structured output are unreliable on a workload, simplify the prompt and tool set before testing an escalation to Sol.

Capabilities

GPT-5.6 previewFunction callingStructured outputStreaming responses

Recommended Scenarios

  • Product default candidate
  • SaaS integrations
  • Workflow automation
  • Multi-turn assistants

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
gpt-5.6-terra
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 SDK, Cursor, and cURL.

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": "gpt-5.6-terra", "messages": [...] }
Anthropic / Claude
Base URL
https://api.gpt88.cc
Endpoint
POST /v1/messages
Body
{ "model": "gpt-5.6-terra", "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: gpt-5.6-terra. 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 gpt-5.6-terra.
  • 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 gpt-5.6-terra 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": "gpt-5.6-terra",
    "messages": [
      {"role": "user", "content": "Introduce gpt88.cc in one sentence."}
    ]
  }'

Expected response (trimmed example):

200 OKjson
{
  "id": "chatcmpl-gpt-5-6-",
  "object": "chat.completion",
  "created": 1730000000,
  "model": "gpt-5.6-terra",
  "choices": [
    {
      "index": 0,
      "finish_reason": "stop",
      "message": { "role": "assistant", "content": "..." }
    }
  ],
  "usage": { "prompt_tokens": 24, "completion_tokens": 64, "total_tokens": 88 }
}