While this compatibility layer is fully supported, our priority remains the reliability and performance of the native Neosantara AI API. For the best experience and access to our complete feature set, we recommend using our modern
/v1/responses endpoint.Getting Started
To use the OpenAI SDK, you only need to change three things in your existing code:- Update the
base_urlto point to Neosantara AIβs API endpoint. - Replace your API key with a Neosantara AI API key.
- Update the model name to a Neosantara AI model.
Feature Compatibility Details
While we aim for maximum compatibility, there are some differences in how certain features are implemented.System / Developer Messages
The concept of asystem prompt is fully supported. For some underlying providers that donβt have a native system role, the content of your system message will be automatically prepended to the first user message to ensure the model follows your instructions.
Reasoning
Neosantara AI supports advanced reasoning through a specialreasoning parameter available in both the /v1/responses and /v1/chat/completions endpoints.
Conversation State (store)
The store: true and previous_response_id parameters are fully supported in the /v1/responses endpoint. This allows you to build stateful conversations without manually resending the entire chat history. This feature is not available for /v1/chat/completions.
Tools
The endpoint supports OpenAI-compatible function calling. See Tools Overview for details.Detailed Parameter Support
Most unsupported fields are silently ignored to prevent errors.| Field | Support Status & Notes |
|---|---|
model | Fully supported. Use Neosantara AI model names. |
messages | Fully supported in /v1/chat/completions. |
input / instructions | Fully supported in /v1/responses. |
max_tokens | Fully supported. |
stream | Fully supported for both endpoints. |
temperature | Fully supported. |
top_p | Fully supported. |
stop | Fully supported. |
presence_penalty | Fully supported. |
frequency_penalty | Fully supported. |
response_format | Fully supported. json_schema is only available in /v1/responses. |
tools / functions | Fully supported. strict mode is handled on a best-effort basis by the underlying provider. |
tool_choice | Fully supported. |
n | Ignored. Only one choice (n=1) is supported. |
logprobs / top_logprobs | Ignored. |
user / metadata | Ignored. |
seed | Ignored. |