GPT88 / API Docs
ChatOpenAIFeatured1 vendors

gpt-6.1-terra

GPT-6.1 Terra for visual reasoning, computer use, and everyday professional work.

Get API Key on gpt88.ccQuickstart

Overview

  • OpenAI describes GPT-6.1 Terra as a fast, efficient model for visual reasoning, precise computer use, and clear, natural writing. Its examples include matching product photos to catalog entries, interpreting technical drawings, acting on application screens, and drafting or revising text.
  • The OpenAI API catalog lists a 1.05M context window, 128K maximum output, image input, text input and output, and reasoning effort from none to max. OpenAI standard API prices are $1 per million input tokens and $5 per million output tokens; GPT88 pricing and available specifications are set by its console.
  • OpenAI reports that Terra scored 15 percentage points above GPT-5.6 Terra on Agents’ Last Exam at medium reasoning effort at about one-third the cost, and scored 50.3% on Terminal-Bench 4.0 at max effort. These are provider-reported results, not independent evaluations or guarantees for GPT88 routes.

Best Use Cases

  • Understand images, product photos, interfaces, or technical drawings
  • Complete multi-step tasks in desktop or application interfaces
  • Handle everyday professional work, drafting, and editing
  • Evaluate the balance of quality, speed, and cost on visual and computer-use tasks

Integration Notes

  • Use the GPT88 OpenAI-compatible API and set the request model to gpt-6.1-terra.
  • OpenAI lists /v1/responses and /v1/chat/completions; tool calling requires the Responses API. Confirm which endpoints, tools, and parameters the current GPT88 API key can use.
  • The OpenAI API supports reasoning.effort values none, low, medium, high, xhigh, and max. Confirm route support with the GPT88 console or a minimal request.

Usage Notes

  • The $1/$5 per million token rates are OpenAI standard API prices, not GPT88 prices. Check GPT88 billing, access, quota, rate limits, and routes in the console.
  • Published benchmark figures are provider-reported and may not reproduce with GPT88 routes, prompts, or tool environments.
  • Access, groups, quota, pricing, rate limits, and available routes may vary by API key.

Capabilities

Visual reasoningComputer useImage understandingCode and tool useNatural writing

Recommended Scenarios

  • Image and technical-drawing analysis
  • Desktop app automation
  • Image-to-catalog matching
  • Everyday writing and editing
  • High-volume professional work

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

Expected response (trimmed example):

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