GPT Chat Completions

Call GPT-6.1 Sol, GPT-6 Astra, GPT-6 Sol and GPT-6 Luna through one OpenAI Chat Completions endpoint with a BeatAPI key.

• One endpoint, POST /v1/chat/completions, for every current GPT model. Change model to switch.
• Text and image input, text output, streaming, function calling, structured outputs and configurable reasoning effort.
• Works with the OpenAI SDK: change the base URL and use a BeatAPI key.
• For new reasoning and tool-calling integrations, OpenAI Responses is the recommended format.

Opens this endpoint in the API Explorer. Enter your BeatAPI API key and send: the call is real and is billed to your own balance.

Models

Send one of these IDs as model. Each is a separate model; do not treat them as aliases of each other.

• Prices are the base tier, discount already applied. A long-context tier, cached-input rates and cache writes are not in this table; see the price table.
• — means the catalogue does not publish the number.

Older IDs of this family still work and are listed on Legacy models.

Quick start

Install the openai package on your server, keep the key in BEATAPI_API_KEY, and never put it in browser code. These are request examples, not recorded model outputs.

Read the answer from choices[0].message.content, then check finish_reason and usage. An HTTP 200 alone does not prove the answer satisfies your task: validate it in your application. Text requests return directly; do not poll /v1/tasks for them.

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

Endpoint and authentication

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

Request parameters

Standard OpenAI Chat Completions fields are accepted. Request-format compatibility does not mean every provider-specific option or tool is supported, so test the options you rely on.

Response

A non-streaming call returns one JSON object. This is an abbreviated example.

{
  "id": "chatcmpl-example",
  "object": "chat.completion",
  "created": 1791993600,
  "model": "gpt-6-luna",
  "choices": [
    {
      "index": 0,
      "message": {
        "role": "assistant",
        "content": "Retry with exponential backoff and jitter, and make every handler idempotent."
      },
      "finish_reason": "stop"
    }
  ],
  "usage": {
    "prompt_tokens": 19,
    "completion_tokens": 16,
    "total_tokens": 35
  }
}

Response fields

Streaming

Set "stream": true. BeatAPI forwards the server-sent event stream without converting it, so event objects stay compatible with the OpenAI SDK.

• The response is text/event-stream; without streaming it is application/json.
• A failure before the model is called is returned as a normal JSON error with an HTTP status, not as a stream event.
• Set explicit timeouts and reconnect a streamed response safely.

data: {"id":"chatcmpl-example","object":"chat.completion.chunk","choices":[{"index":0,"delta":{"role":"assistant","content":"Retry"},"finish_reason":null}]}
data: {"id":"chatcmpl-example","object":"chat.completion.chunk","choices":[{"index":0,"delta":{"content":" with backoff"},"finish_reason":null}]}
data: {"id":"chatcmpl-example","object":"chat.completion.chunk","choices":[{"index":0,"delta":{},"finish_reason":"stop"}]}
data: [DONE]

Errors

HTTP errors at a glance

Authentication, routing, rate-limit and unknown-model failures are answered before the model is called, in the BeatAPI envelope: error.code, error.message, retryable, request_id. Every other failure keeps the OpenAI SDK shape {"error": {"message", "type", "code"}}: the code is in error.code and the request id ends message. See Errors.

Full code table and retry policy: Errors.

Notes

• GPT models also answer on OpenAI Responses.
• Above 272K input tokens, gpt-6.1-sol and gpt-6-astra use a higher tier for the full request. See the price table before budgeting a long-context workload.
• Keep API keys on trusted servers, log the response request ID, and retry only 429, 500 and 503.