Strict OpenAI Compliance

In certain scenarios, responses from providers like Perplexity may include additional fields that do not directly correspond to OpenAI fields. To retrieve these fields, use one of the following methods:

Python SDK: Set the parameter strict_open_ai_compliance=false when initializing the Gegentica client.
Node SDK: Set the parameter strictOpenAiCompliance: false when initializing the Gegentica client.
HTTP Requests: Include the header x-gegentic-strict-open-ai-compliance: false in your request.

By default, Gegentica Python and Node SDKs have strict_open_ai_compliance set to false.

Examples

Python SDK
OpenAI Python
cURL

from gegentic import Gegentic

client = Gegentic(
  provider='openai',
  base_url='https://gateway.gegentic-ai.com/v1',
  gegentic_api_key='sk-obg***',  # Your Gegentic API key here
  strict_open_ai_compliance=False,
)

response = client.chat.completions.create(
  messages = [{ "role": 'user', "content": 'Say this is a test' }],
  model = "Qwen/Qwen2.5-32B-Instruct"  # The LLM model tied to the API key
)

from openai import OpenAI
from gegentic import createHeaders

client = OpenAI(
  base_url='https://gateway.gegentic-ai.com/v1',
  api_key='sk-***',  # Your OpenAI API key here
  default_headers=createHeaders(
    provider="openai",
    api_key="sk-obg***",  # Your Gegentic API key here
    strict_open_ai_compliance=False,
  )
)

response = client.chat.completions.create(
  model="gpt-3.5-turbo",
  messages=[{"role": "user", "content": "Hello!"}]
)

curl https://gateway.gegentic-ai.com/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -H "x-gegentic-api-key: $GEGENTIC_API_KEY" \
  -H "x-gegentic-provider: openai" \
  -H "x-gegentic-strict-open-ai-compliance: false" \
  -d '{
    "model": "gpt-4o-mini",
    "messages": [{
      "role": "user",
      "content": "Hello!"
    }]
  }'

Remote MCP Image Generation

Introduction

Features

Support

Strict OpenAI Compliance

Examples

​Examples

Examples