Does Cognocient support the OpenAI Responses API?

Yes. Point the OpenAI SDK's base URL at Cognocient and call client.responses.create(...). Streaming, function tools, structured output (json_schema), image inputs and reasoning effort are supported.

Does it work with non-OpenAI models?

Yes. The request runs through the same pipeline as /v1/chat/completions, so it works with any provider Cognocient supports, including Anthropic, Gemini, Bedrock, Vertex AI, Azure and custom endpoints.

Do budgets, guardrails and the Emergency Freeze apply?

Yes, identically. There is no separate code path: a Responses request is translated to a chat request and goes through the same authentication, rate limits, guardrails, budgets, routing, caching, failover and cost logging.

What is not supported?

Stateful features (previous_response_id, conversation, background mode, stored prompts) and OpenAI-hosted tools (web search, file search, code interpreter, computer use, remote MCP). These return a clear 400 error instead of silently misbehaving.

Can I use the OpenAI Responses API through Cognocient?

Cognocient supports POST /v1/responses, including streaming and function tools, on every provider. Budgets, guardrails, routing, caching and cost tracking apply exactly as they do to chat completions.

Cognocient exposes POST /v1/responses alongside /v1/chat/completions, so code written against OpenAI's newer Responses API works with a one-line base-URL change.

from openai import OpenAI
 
client = OpenAI(base_url="https://api.cognocient.com/v1", api_key="<your proxy key>")
 
resp = client.responses.create(
    model="gpt-4o",
    instructions="Answer in one sentence.",
    input="Why is the sky blue?",
)
print(resp.output_text)

Streaming works the same way (stream=True), emitting the standard response.output_text.delta, response.function_call_arguments.delta and response.completed events.

How it works

Cognocient translates the Responses request into a chat request, runs it through the same pipeline as /v1/chat/completions, and translates the result back. That means everything you already configured applies with no extra setup:

Attribution headers (X-Cost-Feature, X-Cost-User, …) and cost tracking
Budgets, the velocity circuit breaker and the Emergency Freeze
PII / secret / prompt-injection guardrails
The Auto Router, routing rules and load-balanced groups
Semantic caching, provider failover and rate limits
Every provider, not just OpenAI

Calls appear in the dashboard like any other call.

Supported

Feature	Notes
`input` as text or an item list	Messages, `function_call` and `function_call_output` items
`instructions`	Sent as the system message
Streaming	Full Responses event stream
Function tools and `tool_choice`	Including parallel tool calls
Structured output	`text.format` with `json_schema` or `json_object`
Image input	`input_image` with an `image_url`
`max_output_tokens`, `temperature`, `top_p`, `reasoning.effort`	Mapped to the provider's equivalent

Not supported

Cognocient's Responses endpoint is stateless: it keeps no response history. These return a 400 with code: "unsupported_parameter":

previous_response_id, conversation: send the full conversation in input instead
background mode and stored prompt templates
Hosted tools that run on OpenAI's servers: web_search, file_search, code_interpreter, computer_use, remote mcp
File-ID inputs (input_image needs a URL, input_file is not supported)

store and metadata are accepted and ignored. Responses are never stored.

Calls made through /v1/responses are recorded with the same endpoint label as chat completions, so they are not separated in endpoint breakdowns.

Can I use the OpenAI Responses API through Cognocient?

How it works

Supported

Not supported

On this page