OpenAI SDK on a confidential,
EU-controlled endpoint.
Same from openai import OpenAI. Same client.chat.completions.create(). One line changes, base_url now points at https://api.voltagegpu.com/v1, and every request goes to a model in an Intel TDX enclave, through our relay.
No fork. No proprietary client. No code rewrite. Migrate a production agent this afternoon and keep your existing tests, retries and middleware.
Requests pass through our relay, which sees them in clear (TLS ends at our host). To keep plaintext off our servers, run your own inference server in a Confidential VM and terminate TLS inside its trust domain. Confidential VMs
Why teams swap base_url
Calling api.openai.com is fine for many workloads. It stops being fine the moment a prompt carries privileged client documents, regulated personal data, or work product covered by an NDA. Three forces typically push engineering teams to a sovereign endpoint.
Schrems II + FISA 702 exposure
EU controllers cannot cleanly justify routing privileged or personal data through US-controlled inference. VoltageGPU is operated by VOLTAGE EI, a French controller, under an RGPD Art. 28 DPA; compute sub-processors are listed and the transfer is documented once.
Training-data leakage risk
Even with retention disabled, prompts sit in the provider's memory in cleartext. Here the model runs inside an Intel TDX trust domain: the host and its hypervisor see encrypted memory, not your prompts; our relay sees them in clear on the way.
Evidence you check yourself
GET /v1/attestation returns the Intel TDX quote and NVIDIA GPU evidence of the instances serving a model, bound to a nonce you choose. Archive it next to your logs. It covers the instances, not each response.
Three-step migration
Start from a working OpenAI integration. Three changes, no patched SDK, no custom client.
Install the official OpenAI SDK
pip install openai (>=1.40.0) for Python or npm install openai (^4.60.0) for Node. No fork from VoltageGPU, exact same package as on openai.com.
Set base_url and api_key
base_url = "https://api.voltagegpu.com/v1" and api_key = "vgpu_..." from voltagegpu.com/api-keys. The SDK constructor accepts both, no monkeypatching.
Pick a -TEE model
Replace your model parameter (e.g. "gpt-4o") with a confidential one: gemma-4-31B-turbo-TEE, Qwen3.5-397B-A17B-TEE or DeepSeek-V3.2-TEE.
Python, full working examples
The four examples below cover what most production workloads actually use: chat, streaming, tool calling, structured outputs, and the async client.
Node / TypeScript, full working examples
The official openai package on npm. Works in Node, Edge runtimes (Vercel, Cloudflare Workers) and Bun.
OpenAI feature compatibility matrix
What lives under /v1/chat/completions works on -TEE models: streaming, tools, JSON mode. Embeddings, Assistants, Batch and fine-tuning are not offered on the confidential endpoint.
Models on the OpenAI-compatible endpoint
Only models with the -TEE suffix are exposed on the confidential endpoint, every other model name is rejected with a clear 400. The model name is what you pass to the model parameter on the OpenAI client.
Default worker model. Fast, low-cost agent loops.
Long-context drafting, contract review, RAG over large corpora.
Reasoning chains, IC memos, deep analysis with chain-of-thought.
Per million tokens, from our live pricing.
Latency, regions and edge runtimes
TTFT
Time-to-first-token depends on the model and the prompt length. Measure it on your own traffic: a first call costs a fraction of a cent.
Isolated by hardware, not by a map
The model runs inside Intel TDX enclaves, so the host cannot read the trust domain wherever the capacity sits. French controller, EU-hosted customer database, GPU capacity operated in the US. Our relay sees requests in clear on the way in.
Edge runtime support
The OpenAI Node SDK works on Vercel Edge, Cloudflare Workers, Bun and Deno. Streaming uses standard SSE, no special transport.
Authentication and rate limits
Inference keys start with vgpu_
Create and revoke them at voltagegpu.com/api-keys. Usage is billed per token from your account balance.
Rate limits
Past a rate limit the API answers 429, which the OpenAI SDK retries on its own.
TLS ends on our relay
TLS ends on our API, which forwards each request in clear to the model in a TDX enclave. Inside the enclave, the hypervisor and host operators see encrypted memory.
Attestation reports (opt-in)
GET /v1/attestation returns the Intel TDX quotes and NVIDIA GPU evidence of the TEE model instances, bound to a nonce you choose, so you can check the hardware yourself. It attests the instances serving the model, not each completion.
Pricing
Pay per token at the live rates above, from your account balance, with no subscription. There is no surcharge for the confidential endpoint. Every -TEE model and its current price is on the pricing page.
What confidential actually means here
A model instance in Intel TDX
Your request reaches our API over TLS; our relay forwards it in clear to a model instance inside an Intel TDX trust domain, where the host and its hypervisor see encrypted memory.
Memory encryption by the CPU
Keys held by the CPU encrypt the trust domain's memory. A memory dump from the host yields ciphertext, not your contracts or patient notes.
Attestation on your own nonce
GET /v1/attestation returns the TDX quote and NVIDIA GPU evidence of the instances serving a model, verifiable against Intel and NVIDIA. It covers the instances, not each response.
No training reuse
We never use prompts or completions for training. RGPD Article 28 DPA, EU jurisdiction (VOLTAGE EI, France).
Frequently asked questions
Do I really not have to change my code?
You change three lines: the base_url, the api_key, and the model name (the exact -TEE id from GET /v1/models, such as google/gemma-4-31B-turbo-TEE). client.chat.completions.create(), the streaming iterator, the async client, tool calling and response_format keep working because the wire format is OpenAI-compatible. Embeddings are the exception: no confidential embedding model is offered yet. Requests pass through our relay, which sees them in clear (TLS ends at our host). To keep plaintext off our servers, run your own inference server in a Confidential VM and terminate TLS inside its trust domain.
Is the OpenAI SDK actually unmodified?
Yes. We test against pip install openai (>=1.40.0) and npm install openai (^4.60.0), the official packages from openai/openai-python and openai/openai-node. There is no VoltageGPU fork. If a future SDK version breaks compatibility, we treat it as a P1 bug on our side.
Which base URL and which key?
Base URL https://api.voltagegpu.com/v1, with an inference key that starts with vgpu_, created at voltagegpu.com/api-keys and sent as a Bearer token, which the OpenAI SDK does for you. GPU machine keys are different: they start with volt_ and go in an X-API-Key header.
How do I keep using the OpenAI SDK against api.openai.com for some calls?
Instantiate two clients. One with base_url defaulted (api.openai.com) for non-sensitive workloads, and one with base_url=https://api.voltagegpu.com/v1 for confidential workloads. Pick the client at the call site, or wrap them behind a small router by data-classification.
Are my prompts logged?
Billing keeps the model name, token counts and the status code; our API relay sees the prompt and the completion in clear while forwarding them. Your request reaches our API over TLS and is relayed to a model instance running inside an Intel TDX trust domain with a confidential-computing GPU.
Does it work with LangChain, LlamaIndex, CrewAI, AutoGen, Vercel AI SDK?
Yes, every framework that lets you set base_url and api_key on its OpenAI provider works. See /langchain-tee-deployment, /crewai-private-deployment, and /mcp-server-confidential for full setups. Vercel AI SDK works via createOpenAI({ baseURL, apiKey }).
Can I prove a request actually ran inside Intel TDX?
For the instances, not for each response. GET /v1/attestation?model=<id>&nonce=<64 hex> returns, for every instance serving that model, an Intel TDX quote and the NVIDIA GPU evidence bound to the nonce you chose, which you verify yourself. It proves those instances are genuine TDX guests with confidential-computing GPUs. It does not prove that a given response came from one of them, or which code they run.
EXPLORE FURTHER
Swap base_url, ship before lunch
Create a vgpu_ inference key, change three lines, keep your existing OpenAI SDK code. Requests pass through our relay, which sees them in clear (TLS ends at our host). To keep plaintext off our servers, run your own inference server in a Confidential VM and terminate TLS inside its trust domain.