Skip to content

The Open Standard for Generative UI

docs: remove unsupported request-level BYOK (#1022)

Visharad Kashyapc85caed29dcd
diff --git a/docs/content/docs/openui-cloud/api/chat-completions.mdx b/docs/content/docs/openui-cloud/api/chat-completions.mdx
index 82648e619..08c9f9224 100644
--- a/docs/content/docs/openui-cloud/api/chat-completions.mdx
+++ b/docs/content/docs/openui-cloud/api/chat-completions.mdx
@@ -1,5 +1,5 @@
---
-title: Chat Completions (Embed)
+title: Chat Completions
description: "Use the OpenAI-compatible embed endpoint for text, managed or self-hosted generative UI, and function tools."
---
@@ -116,14 +116,3 @@ const completion = await embedClient.chat.completions.create({
```
In this mode, prompt assembly, output validation, and rendering are owned by your application.
-
-### Request-level provider key
-
-For a request-level self-hosted key flow, encrypt the provider key with `POST /encryption/encrypt`, then include this object in the request body:
-
-```ts
-byok: {
- provider,
- encryptedApiKey,
-}
-```