GPT-5.6 API

GPT-5.6 is available in three production tiers. All three support text and image input, text output, streaming, function calling, structured outputs, and configurable reasoning effort.

Recommended: Responses API

Use the Responses API for new reasoning and tool-calling integrations.

1
import OpenAI from "openai";
2
3
const client = new OpenAI({
4
  apiKey: process.env.BEATAPI_API_KEY,
5
  baseURL: "https://api.beatapi.io/v1"
6
});
7
8
const response = await client.responses.create({
9
  model: "gpt-5.6-terra",
10
  input: "Design a resilient webhook retry strategy for a payments API.",
11
  reasoning: { effort: "medium" }
12
});
13
14
console.log(response.output_text);

$
curl --request POST \
>
  --url https://api.beatapi.io/v1/responses \
>
  --header 'Authorization: Bearer <BEATAPI_API_KEY>' \
>
  --header 'Content-Type: application/json' \
>
  --data '{
>
  "model": "gpt-5.6-terra",
>
  "input": "Design a resilient webhook retry strategy for a payments API.",
>
  "reasoning": {
>
    "effort": "medium"
>
  }
>
}'

Reasoning effort accepts none, low, medium, high, xhigh, and max. Use medium as a balanced starting point, then evaluate one level lower and higher on your own workload.

Existing SDK formats

You can migrate an existing integration by changing the base URL and replacing the provider key with a BeatAPI key.

OpenAI Chat Completions

POST https://api.beatapi.io/v1/chat/completions

$
curl --request POST \
>
  --url https://api.beatapi.io/v1/chat/completions \
>
  --header 'Authorization: Bearer <BEATAPI_API_KEY>' \
>
  --header 'Content-Type: application/json' \
>
  --data '{
>
  "model": "gpt-5.6-terra",
>
  "messages": [
>
    {
>
      "role": "user",
>
      "content": "Design a resilient webhook retry strategy for a payments API."
>
    }
>
  ]
>
}'

Anthropic Messages

POST https://api.beatapi.io/v1/messages

Send the BeatAPI key with x-api-key or Authorization: Bearer.

$
curl --request POST \
>
  --url https://api.beatapi.io/v1/messages \
>
  --header 'Authorization: Bearer <BEATAPI_API_KEY>' \
>
  --header 'Content-Type: application/json' \
>
  --data '{
>
  "model": "gpt-5.6-terra",
>
  "max_tokens": 1024,
>
  "messages": [
>
    {
>
      "role": "user",
>
      "content": "Design a resilient webhook retry strategy for a payments API."
>
    }
>
  ]
>
}'

Gemini-compatible content

POST https://api.beatapi.io/v1beta/models/{model}:generateContent

Send the BeatAPI key with x-goog-api-key, Bearer authentication, or the Gemini SDK-compatible key query parameter. Prefer the header for direct HTTP integrations.

$
curl --request POST \
>
  --url 'https://api.beatapi.io/v1beta/models/gpt-5.6-terra:generateContent' \
>
  --header 'Authorization: Bearer <BEATAPI_API_KEY>' \
>
  --header 'Content-Type: application/json' \
>
  --data '{
>
  "contents": [
>
    {
>
      "role": "user",
>
      "parts": [
>
        {
>
          "text": "Design a resilient webhook retry strategy for a payments API."
>
        }
>
      ]
>
    }
>
  ]
>
}'

Streaming

Set the streaming field expected by your selected format. BeatAPI forwards the server-sent event stream without converting it, so event names and response objects remain compatible with that SDK format.

Authentication and availability

List the currently enabled text models before rollout:

$
curl https://api.beatapi.io/v1/models \
>
  -H "Authorization: Bearer $BEATAPI_API_KEY"

1
{
2
  "object": "list",
3
  "data": [
4
    { "id": "gpt-5.6-terra", "object": "model", "owned_by": "beatapi" }
5
  ]
6
}

The same API key and USD balance are shared across Text, Image, Video, Workflow, Effect, and Realtime APIs. Calls are metered from actual token usage; inspect request IDs, model, token totals, status, and settled amount in Dashboard usage logs.

Production checklist

• Keep API keys on trusted servers and redact them from logs.
• Set explicit request timeouts and reconnect streamed responses safely.
• Log the response request ID for support and billing audits.
• Evaluate model tier and reasoning effort on representative production inputs.
• Handle 401, 402, 429, 502, and 503 as distinct operational cases.

Continue with media models

The same BeatAPI account can call GPT Image 2, MiniMax H3, Seedance 2.5, and the rest of the Image and Video APIs without adding another billing or authentication system.