From 85c12a2038157b18dfa04ecd3d6db9702aab0c05 Mon Sep 17 00:00:00 2001
From: Seven <246023385+seven7763@users.noreply.github.com>
Date: Mon, 3 Aug 2026 10:05:16 +0800
Subject: [PATCH] docs: note OpenAI client base_url for multi-model gateways

Clarify that the same base_url client pattern used with LocalAI also works
with OpenAI-compatible multi-model gateways, using DaoXE as one example.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---
 docs/content/faq.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/content/faq.md b/docs/content/faq.md
index 73623df37874..07a2681da1cf 100644
--- a/docs/content/faq.md
+++ b/docs/content/faq.md
@@ -72,8 +72,11 @@ See the performance section of the runtime errors reference: {{% relref "referen
 
 Yes! If the client uses OpenAI and supports setting a different base URL to send requests to, you can use the LocalAI endpoint. This allows to use this with every application that was supposed to work with OpenAI, but without changing the application!
 
+> **Tip:** The same `base_url` client pattern works with any OpenAI-compatible multi-model gateway when you are not self-hosting — for example [DaoXE](https://daoxe.com/?utm_source=github&utm_medium=organic&utm_campaign=localai&utm_content=pr) at `https://api.daoxe.com/v1`.
+
 ### Can this leverage GPUs? 
 
+
 There is GPU support, see {{%relref "features/GPU-acceleration" %}}.
 
 ### Where is the WebUI?