# BranderUX

> Build agentic applications, in minutes. One message in. Your full agentic application out: website and MCP app, live. Describe your business and a real AI agent builds your application in front of you: your brand, your real data, interactive screens (dashboards, catalogs, tables, charts, forms) generated live, per customer, per question. Publish with one click and your application is live for people and for AI agents.

App builders generate pages once, the same app for everyone. A BranderUX application is generated live: every screen is built at the moment of the question, with the right UX for that user and that action, and every click becomes the next question. Your website talks with your clients, by your rules: you decide what the AI can do, which actions wait for the visitor's click and who gets in, your data stays yours, and every conversation is visible to you. Screens compose from certified branded elements, or custom elements you create in Vibe Studio, the built-in AI element builder, from a description or a screenshot.

Companies that already have an agent connect it as a first-class capability: one React component, any framework (LangGraph, CrewAI, Google ADK, Pydantic AI, Mastra, or custom), provider-agnostic across Claude, GPT, and Gemini. Two-Phase Architecture means BranderUX never sees or stores your data, your agent fills the screens on your side.

## For business owners

- [What is an agentic app?](https://branderux.com/docs/build): An AI agent that meets your customers and answers with real, branded, interactive screens, built from a conversation, connected to your real data, live at your own address.
- [Your first build](https://branderux.com/docs/build/first-build): Describe your business once. The Builder finds your site, extracts your brand, connects your real data, and assembles a working agentic app while you watch.
- [Your data](https://branderux.com/docs/build/data): Four ways to give your agent the truth: live store feeds, your own files and photos, any API your business runs, and connected apps with managed sign-in.
- [Screens and your home page](https://branderux.com/docs/build/screens): Bespoke components composed into screens the agent fills per question, and a designed home page that opens instantly with live data on every visit.
- [Test and publish](https://branderux.com/docs/build/publish): Try the real agent on your real data, publish your full application in one click, and understand usage limits and human handoff.
- [Add it to your own site](https://branderux.com/docs/build/widget): Wix, WordPress, Shopify, Squarespace or plain HTML: one line, and your agent answers on the site you already have.
- [Receive records by webhook](https://branderux.com/docs/build/webhooks): Every new and updated lead, booking, order and request, sent to your own system and signed so you can check it came from us.
- [Pricing](https://branderux.com/pricing): Free to build. Free to publish. Pay for the conversations your agent has. Every plan is the full product.

## Live examples

Six demo businesses, each a live agentic application built on BranderUX; the same address with `/mcp` on the end is its MCP app.

- [Brandeck](https://brandeck.branderux.app): a deck builder's Agentic Salesperson, on a landing page.
- [Brandoria](https://brandoria.branderux.app): a restaurant's Agentic Waiter.
- [Barbrander](https://barbrander.branderux.app): a barbershop's Agentic Receptionist.
- [Brandelia](https://brandelia.branderux.app): a flower studio's Agentic Florist.
- [Brand & Breakfast](https://brand-and-breakfast.branderux.app): a bed and breakfast's Agentic Concierge.
- [Brandazaar](https://brandazaar.branderux.app): a gift shop's Agentic Shop Assistant.
- [Atelier Nova](https://nova.branderux.app): a womenswear store with no pages: every screen is generated live by the agent BranderUX hosts for it, and the frontend is one `<Brander>` component. Open source: [github.com/BranderUX/atelier-nova](https://github.com/BranderUX/atelier-nova).

## Developer documentation

- [Introduction](https://branderux.com/docs): What BranderUX is and how the pieces fit together.
- [Installation](https://branderux.com/docs/installation): Install `@brander/sdk` and add the `<Brander>` widget.
- [Quick Start](https://branderux.com/docs/quickstart): From npm install to a rendering widget, including the backend AG-UI SSE endpoint.
- [Choosing your integration](https://branderux.com/docs/guides/choosing-an-integration): Pick the BranderUX integration path that fits your stack, client adapters (no server), a BYO-backend SSE endpoint, the zero-dependency Embed, or an MCP App.
- [Fixed screens vs flexible](https://branderux.com/docs/guides/modes): BranderUX's two UI modes, who controls the layout, how the UI streams in, and which fits your use case. Fixed Screens (deterministic) vs Flexible (A2UI).
- [Building a server AG-UI endpoint](https://branderux.com/docs/guides/server-adapter): For agents that run server-side: the nested {params} request body, the AG-UI SSE wire format, and a copy-paste Node and Python/FastAPI reference adapter.

## API reference

- [Brander component](https://branderux.com/docs/api/brander): The `<Brander>` widget API.
- [Props](https://branderux.com/docs/api/props): `BranderProps`: apiKey, projectId, onQuery/onQueryStream (optional in hosted mode), variants.
- [Types](https://branderux.com/docs/api/types): `CustomerAIParams`, `MultiProviderTools`, and the AG-UI event types.

## Components

- [Brander](https://branderux.com/docs/components/brander): Inline embeddable widget.
- [Chat Widget](https://branderux.com/docs/components/chat-widget): Floating, expandable chat widget.

## Examples

- [AI agents](https://branderux.com/docs/examples/agents): LangGraph / CrewAI / Google ADK / Pydantic AI backends.
- [Chat support](https://branderux.com/docs/examples/chat-support): Support assistant integration.
- [E-commerce](https://branderux.com/docs/examples/ecommerce): Product catalog and assistant.
- [SaaS dashboard](https://branderux.com/docs/examples/saas): Analytics and pipeline UI.
- [Custom](https://branderux.com/docs/examples/custom): Building custom integrations.

## MCP server (build from any AI client)

- [BranderUX MCP](https://branderux.com/mcp): Remote MCP server: build and control BranderUX applications (projects, brand, custom elements, screens, API keys) from Claude, ChatGPT, Cursor, VS Code or any MCP client.
- Endpoint: `https://mcp.branderux.com/mcp` (Streamable HTTP; OAuth 2.1 browser sign-in with PKCE, no API keys to paste).
- Registry: published in the official MCP Registry as `com.branderux/mcp`.
- Elements and screens render as live interactive MCP apps in supported clients; `generate_screen` renders a branded screen in the chat with or without a project.
- Access: anyone with a BranderUX account; the first call opens your browser for a one-click sign-in.

## SDK & access

- [@brander/sdk on npm](https://www.npmjs.com/package/@brander/sdk): The React SDK package.
- Which agent answers is your call: with no handler the project's BranderUX-hosted agent answers inside your app (no backend, no model keys); pass `onQueryStream` to connect the agent you already have. Not a React site? The one-line widget does the same integration: https://branderux.com/docs/build/widget
- Start at [branderux.com](https://branderux.com): describe your business and sign in with Google; the Free plan is the full product. Questions via the [contact form](https://branderux.com/contact).