Quinta speaks the same language as the OpenAI API. That means you don’t have to rewrite your applications to move from a cloud service to your own sovereign AI. It’s enough to change one setting — the base_url.
The principle: only the address changes
Every OpenAI-compatible client sends its requests to a base_url. By default that points to OpenAI’s servers. Point the base_url at your Quinta instance instead, and the same requests go to your own infrastructure — answered there by the models you run on your hardware.
In concrete terms you change just two values:
- the base_url — pointing to your Quinta instance's endpoint (ending in /v1),
- the API key — issued by your Quinta dashboard, not OpenAI's.
The model name comes from your Quinta catalogue. Otherwise your code stays unchanged — all calls, libraries and tools keep working.
To be clear: you are not routing your OpenAI traffic „through“ Quinta. You replace the endpoint — requests go to Quinta instead of OpenAI and are answered by your local models. Not a single byte leaves the building.
Where to find the base_url and key
Both values are in your Quinta dashboard. The endpoint URL has the form https://quinta.your-domain.example/v1 (your actual domain); the API key is issued per user or application and can be revoked there too.
Switched in a few lines
Pick your language or framework. It’s the same change every time — point the base_url and key at Quinta:
from openai import OpenAI
client = OpenAI(
base_url="https://quinta.your-domain.example/v1",
api_key="QUINTA_API_KEY",
)
response = client.chat.completions.create(
model="llama-3.1-8b-instruct",
messages=[{"role": "user", "content": "Hello Quinta!"}],
)
print(response.choices[0].message.content)No code change: via environment variables
If you’d rather not touch the code at all: the official OpenAI libraries (Python and Node) read the base_url and key automatically from environment variables. Set them, and your existing application talks to Quinta — without changing a line of code.
export OPENAI_BASE_URL="https://quinta.your-domain.example/v1"
export OPENAI_API_KEY="QUINTA_API_KEY"The exact variable name can differ by SDK; the official OpenAI libraries use OPENAI_BASE_URL and OPENAI_API_KEY.
Check that it works
A quick test: query the available models. If a response comes back from your Quinta instance, the switch was successful.
curl https://quinta.your-domain.example/v1/models \
-H "Authorization: Bearer $QUINTA_API_KEY"What this means for your data
From the moment the base_url points to Quinta, your prompts and the responses no longer leave your infrastructure. An external cloud call becomes a request that stays entirely under your control — the basis for GDPR, the EU AI Act and NIS2. Same API, same tools, but your data stays with you.
The exact values — endpoint URL, API key and the available model names — are in your Quinta dashboard. Our team supports you during rollout.
We'll connect your applications with you.
In the demo we switch a first application to your Quinta instance together — from the base_url to the first production response.