White-label & custom apps
Go beyond the widget. Drive agents from your own product over the API to build fully custom, white-labeled experiences — support desks, in-app copilots, even game characters.
The API is the product
The embeddable widget is the fastest way to ship, but it's just one client of the platform API. When you want a fully custom, white-labeled experience — your brand, your UI, your flows — drive the agents directly over the REST API. No agent4.io branding, no iframe.
What you can build
- In-app copilots — an assistant embedded natively in your product, grounded in your docs.
- Branded support desks — your own chat UI, your domain, backed by agent4.io retrieval and memory.
- Voice & IVR — pipe transcribed audio in, speak the reply out.
- Game & interactive characters — give an NPC a persistent memory and a knowledge base, and drive its dialogue through the API so it stays in character and remembers each player across sessions.
- Automation & backends — no UI at all: call the API from workflows to answer, classify, or draft.
How it works
Use proxy mode: your backend holds the tenant API key and asserts each end user's identity with
X-End-User (see Authentication). The platform gives every end user their
own isolated space — history, memory, and documents — so a game gives each player their own persistent
character relationship, and a SaaS gives each customer their own private assistant.
Everything the widget does, the API does — retrieval, memory, tools, multi-language, follow-ups. The widget is a reference client; your app is a first-class one.
Keeping it white-label
- Serve your own UI; call the API server-to-server so keys never reach the browser.
- Map your user IDs straight to
X-End-User— no separate account system required. - Bring your own domain, styling, and voice; the platform stays invisible to your end users.