
Usage, cost, and corrections
in a single view
See usage and costs across generation and delivery, along with how often Gateway repairs invalid output.
An OpenAI-compatible API that validates and repairs model output against your component library as it streams.
OpenUI GatewayProduction reliability for OpenUI
An OpenAI-compatible API that validates and repairs model output against your component library as it streams.
Every failed generation still returns 200. Based on 1,285 production failures observed over 15 days.
OpenUI matches or beats Google A2UI and Vercel json-render on structural validity, with about half the tokens and streaming time. Better models reduce the error rate. None get it to zero
Every response is validated against your component library. Invalid ones are repaired in the streaming path. Over 99% render successfully.

Tokens are billed at model providers’ standard rates.
Chat Completions and Responses endpoints work with your existing SDKs.
Use your existing OpenAI, Anthropic, or Google Vertex credentials and commitments.
Run Gateway behind Portkey or any other OpenAI-compatible gateway.
Your existing upstream cache configuration continues to work.
Use models listed on models.dev, with more available through OpenRouter.
Create a Gateway key in the OpenUI console.
Use the Gateway endpoint as your base URL and choose any model string from models.dev.
Include your component schema so Gateway can validate each response.
const client = new OpenAI({ apiKey: process.env.THESYS_API_KEY, baseURL: "https://api.thesys.dev/v1/embed",});
const response = await client.chat.completions.create({ model: "openai/gpt-5", messages: [ { role: "system", content: generatePrompt({ thesys: true }) }, ...messages, ],});
in a single view
See usage and costs across generation and delivery, along with how often Gateway repairs invalid output.
Chat Completions requests have zero data retention by default on paid models.
Your data is not used for training, except with free models.
GDPR, SOC 2, and ISO 27001 details are available in the Trust centre.
If a provider is unavailable, Gateway serves the same model through another provider.
View current and historical uptime on our service status page.
Self-hosting and VPC deployments are available on Scale.
Each plan includes monthly API calls and all correction calls. Every response uses an API call plus LLM tokens. Tokens are billed separately at model provider rates.
Gateway plans. Annual billing selected; prices shown per month.
Have another question? Join our Discord.
No. OpenUI works without Gateway. You can call any supported LLM directly and use generatePrompt to create the system prompt.
For production applications, OpenUI Gateway adds validation and automatic corrections for generated UI, model routing, and provider fallbacks through an OpenAI-compatible API.
Your data is not used to train models, except with free models. Chat Completions requests have zero data retention by default on paid models.
Yes. Bring your own key (BYOK) to use your existing OpenAI or Anthropic credits and commitments. BYOK carries no platform fee.
Create a Gateway API key, update your base URL and model, and enable Gateway in your prompt. The integration guide covers the full setup.
You can also give the setup prompt to your coding agent or book a call for help.
Yes. Configure OpenUI Gateway as an OpenAI-compatible endpoint behind Portkey or any other OpenAI-compatible gateway.
Yes. OpenUI Gateway honors your upstream cache configuration.
Corrections use a dedicated model tuned for low latency, which we continue to improve. All correction calls are included in your plan and are not billed separately.
No. OpenUI Gateway and OpenUI Observability work independently. Gateway does not require Observability.
We recommend using both. Gateway makes generated UI more reliable. Observability shows what users experienced and whether it worked.