What to call things
Use BrainSite for the public profile, Agent for the visitor-facing AI, Knowledge for approved facts and sources, Directory for public discovery, and Inbox for conversations, leads, and follow-up.

BrainSite is your agent-powered profile. It can live on your website, work as your bio link, and appear in the BrainSite Directory so people can ask about your work before they reach out.
Use BrainSite for the public profile, Agent for the visitor-facing AI, Knowledge for approved facts and sources, Directory for public discovery, and Inbox for conversations, leads, and follow-up.
Create or scan your BrainSite, review your profile, add your projects and links, connect proof sources where available, add knowledge, then test the agent.
Dashboard shows status. Agent controls your public profile. Knowledge controls answers. Inbox stores conversations. Sales Agent controls qualification and booking. Account manages owner details, integrations, and privacy.
Copy your public BrainSite URL from the Agent page, paste it into the website or link field on X, LinkedIn, YouTube, email, or your link-in-bio tool, then test it from a signed-out browser.
A public profile that shows your work, proof, links, and visitor-facing agent in one place.
Visitors ask questions and the agent answers from approved context, sources, and profile data.
Approved source material, corrections, and teaching become reusable business memory.
Review conversations, captured contacts, qualification status, intro requests, and follow-up opportunities.
Start from your website, X profile, or public work history to generate a draft agent-powered profile.
Your public profile can reflect your work, services, visual style, proof, and preferred contact channels.
BrainSite answers best when its knowledge is source-grounded and reviewed. Read the governed learning method for the distinction between approved knowledge, pending proposals, and conversation context.
Read how BrainSite learnsConversation Memory preserves the minimum useful visitor and conversation context. It remains separate from approved Knowledge Memory.
The inbox turns public chat activity into a reviewable lead workflow.
BrainSite runs on three separated layers. The public agent only answers from Knowledge Memory the owner has reviewed and approved, kept apart from Conversation Memory, which holds just enough context to keep one exchange coherent. Between the two sits a set of deterministic safety rules, fixed checks that run the same way every time rather than depending on model judgment. Owner workflows, including Inbox and the knowledge review queue, sit outside that runtime, so approving what the agent knows is a separate step from the agent using it.
A branded public profile or business page with links, contact channels, QR sharing, and a conversational agent.
A governed runtime that combines approved Knowledge Memory, bounded Conversation Memory, public-source context, and deterministic safety rules.
Dashboard, Inbox, knowledge review, identity controls, integrations, usage, and deployment tools keep the owner in control.
Paid plans use soft conversation limits: your agent keeps responding, and overages apply according to the plan.
BrainSite can support web chat, Telegram, SMS, WhatsApp, X (Twitter) DM, voice/call workflows, email notifications, and seller onboarding depending on configuration.
Add the same BrainSite agent to an external website with one script tag when your account has widget access.
Owners can create scoped API keys for one BrainSite deployment and use REST or the local MCP bridge.
Read API markdownBrainSite appeared in 3 of 10 ChatGPT Search answers and 0 of 10 answers tested in Perplexity, Gemini, Google AI Overviews, and Microsoft Copilot. The largest problem was entity recognition: four platforms described the wrong product or could not connect BrainSite with its official website. Test completed July 29, 2026, published July 30, 2026.
Method: the same 10 queries were entered manually in each platform on July 29, 2026, and checked for a BrainSite mention, a clickable citation, description accuracy, and named competitors. This is a point-in-time observation, not a controlled ranking experiment; results can change as platforms update their indexes and retrieval systems. The next test is planned once the category page, comparison pages, and qualified third-party listings have been indexed.
Use a normal public `https://` website. Localhost, private network, internal, and unsafe redirect targets are blocked.
Add source material, approve pending knowledge, and test again. If provider keys or usage limits are missing, fallback behavior may appear.
Check the public slug, deployment status, publish status, visibility settings, and whether the BrainSite is live or published.
Confirm the file type is supported and the account has storage available. Knowledge uploads and seller document uploads have different limits.
Confirm the Stripe checkout completed. If support is investigating, they should check webhook delivery and plan metadata.
Confirm the channel is connected, webhook URLs are configured, and the owner or deployment mapping exists.
Confirm the plan is Starter or above (or an admin account), X shows Connected in Account > Connections, and the BrainSite is published. X only delivers messages from accounts separate from the one your BrainSite is connected as.