Answers for everyone
Visitors ask about products, prices, features or status. The assistant answers from your public content and systems.
White-label
Busymate AI puts an assistant on your site under your own name. It answers product questions for every visitor. For signed-in customers it can check and change things in their account, through your own systems. We run the assistant; the data and the systems stay yours.
Any visitor
What is your return policy?
You can return anything within 30 days, unworn, for a full refund. Want the link to the policy?
Signed-in customer
Where is my order?
Order 4821 shipped yesterday and should arrive on Thursday. Want the tracking link?
Send it to my office address instead
Product answers for everyone. Account actions only for the signed-in customer — with a confirmation on anything that changes.
Built forAgenciesResellersSaaS productsService businesses
What it is
White-label means the assistant carries your brand and speaks from your data. Every conversation runs through your own systems — answers come from your content, with sources, and actions stay under your control.
Visitors ask about products, prices, features or status. The assistant answers from your public content and systems.
A signed-in customer asks in plain words — “where is my order”, “change my address” — and the assistant does it in your systems, for that customer only.
Requests go to your own systems. You own the data and the rules. Busymate AI provides the assistant and the chat window.
How it works
Your sign-in tells the assistant who the customer is. The assistant tells your systems what it may do for them. Both are short-lived, signed confirmations; no password or key is ever shared.
When a customer is signed in on your site, your site signs a short-lived confirmation and passes it to the assistant. We check it against your public key, so the assistant knows exactly who it is talking to. (For developers: a launch token, ES256, checked against your JWKS.)
When the assistant calls your systems, it carries its own signed confirmation naming that one customer and your connection. Your systems check it and answer for that customer only. (For developers: a signed call token bound to the customer’s subject and your connector.)
Anonymous visitors only ever reach your public tools — account tools stay out of reach without a signed-in customer.
What your developers connect
Your developers expose one connection to your systems (an MCP server). Public actions answer anyone. Account actions receive the signed-in customer and answer for that one person. Two small endpoints complete it: your public key and a sign-in handoff.
Open to any visitor, no sign-in needed.
list_plansProducts and pricesfaq_searchFAQs and how-tosservice_statusService statusEach answer is for the signed-in customer only.
my_ordersMy ordersmy_subscriptionMy subscriptionupdate_profileMy profile — updates confirmed firstConfirmWe give your developers a ready-made starter project in plain Node with no extra dependencies. The actions, the public-key endpoint and the sign-in handoff are already laid out; they fill in the parts that read your data.
Go live
Start from the starter project and wire it to your data — public answers first, then the account actions you want to offer.
One command tries every action and both trust endpoints. All green means you are ready.
Add your connection URL, your sign-in issuer and your public-key URL. The Console checks them for you.
Press publish and your branded assistant is live on your web address. We are here if you want a second pair of eyes.
What you get
The assistant lives at your address, with your name and your look — your own domain if you want one.
Product, pricing and support answers before anyone signs in.
Signed-in customers check orders, subscriptions and settings in plain words.
Anything that changes something waits for a clear yes from the customer.
Every answer comes from your systems on your servers. Nothing is copied into ours.
Businesses run this exact setup today — see a live example below.
Customers
Each one has its own brand, web address and systems — see a live example.
2 businesses live · 14 languages · works with your own systems
Customer support and real account actions for a proxy platform — payouts, devices, and verification, answered through its own API.
support.busyproxy.netSee a live example
Support and onboarding for an SMS-gateway product — from enrolling phones to OTP capture, live on its own support domain.
support.busysms.netSee a live example
Questions
Tell us about your product and we will walk through the setup with you — from the starter project to a live assistant on your own web address.
claude mcp add --transport http busymate-ai https://busymate.ai/mcp