MULTI-TENANT · MULTI-MODEL · BY OPS FORGE

Launch an AI chatbot for any client site — in one line.

One backend, every client a tenant. The bot customizes itself per business — branding, knowledge, lead capture, and booking — as a chat widget, a human-like voice agent, or both. Powered by Claude, GPT, or Gemini.

<script src="https://bot.ops4ge.com/embed.v1.js" data-tenant="acme" defer></script>

How it works

A visitor's message flows through the embedded widget to the model and streams back — and when there's intent, it captures a lead or sends a booking link.

VISITORasks a questionWIDGETembed.js · shadow DOMAI MODELclaude · gpt · geminiLEAD CAPTUREDBOOKING SENT

Everything a client bot needs

Any model, per client

Claude, GPT, or Gemini — chosen per tenant. Same streaming + tools across all three.

🎙

Chat or voice

Add a human-like voice agent (ElevenLabs) that shares the chat bot's knowledge — pick a voice from the console. Either or both, per site.

Streaming + tools

Real-time replies that capture leads and surface Calendly / Meet / Zoom booking buttons.

RAG knowledge

Vector search over each business's docs (Atlas + embeddings) so answers stay grounded.

Shadow-DOM widget

One script tag. Isolated styles that never clash with the host site, themed per brand.

Teams & roles

Sign in with email or Google. Owner / Admin / Member roles, invite teammates — each workspace sees only its own clients.

Agent-native

A CLI (account-linked via `bot-forge login`) and an MCP server — build and manage chatbots from the terminal or with an AI agent.

1

Plug into a site

Paste once before </body>. Swap acme for the client's tenant id — branding loads automatically from /api/config.

<script src="https://bot.ops4ge.com/embed.v1.js" data-tenant="acme" defer></script>
2

Build with agents & code

Create a workspace, then link the CLI with bot-forge login (a quick browser approval — no keys to paste), or hand Bot Forge to an AI agent over MCP. For CI, mint an API key in Console → API keys.

CLI

npx bot-forge

Link your account once, then an interactive shell — branded prompt, tab-complete, live commands.

# link this device to your account (opens the browser):
npx bot-forge login

# launch the interactive shell:
npx bot-forge
#   forge › create acme.json
#   forge › test acme "your hours?"
#   forge › embed acme
MCP

hosted MCP

Let Claude build & manage bots as tools — nothing to install.

claude mcp add --transport http bot-forge \
  https://bot.ops4ge.com/api/mcp \
  --header "Authorization: Bearer bf_live_..."

Get the token from Console → API keys (or reuse a CLI login). Then ask: “Create a chatbot for Acme Plumbing, test it, and give me the embed snippet.” Or /prime a client's repo to auto-build one.

3

Manage everything