Partner integration guide

Your assistant. Your domain. Your data.

Busymate AI white-label puts a branded AI assistant on your site. It answers product questions for every visitor — and for signed-in customers it takes real account actions through your own API. Busymate AI runs the assistant; the data and the tools stay yours.

assistant · on your domain

Any visitor

What plans do you offer?

There are three plans — Starter, Pro, and Business. Starter is free. Want a quick comparison?

Signed-in customer · verified

How much have I earned this month?

You’ve earned $842.10 this month across 12 active devices. Payout is scheduled for the 1st.

Update my payout email to maria@example.com

Ready to update your payout email to maria@example.com — confirm?
ConfirmCancel

Product answers for everyone. Account actions only for the verified customer — with confirmation on anything sensitive.

What it is

One assistant, two audiences

White-label means the assistant carries your brand and speaks from your data. Every conversation runs against tools you host — so answers stay accurate, and actions stay under your control.

Answers for everyone

Anonymous visitors ask about products, pricing, features, or status — the assistant answers instantly from your public tools.

Actions for customers

A signed-in customer asks in plain language — “show my devices”, “how much have I earned” — and the assistant calls your account tools, scoped to that customer alone.

Your data stays home

Traffic goes to your MCP server. You own the tools, the data, and the rules. Busymate AI provides the assistant brain and the chat surface.

How it works

Two directions of trust. No shared secrets.

The integration rests on two short-lived signed tokens — one proves who the customer is, the other proves what the assistant may do. Nothing long-lived is exchanged, and no secret is ever shared between the two platforms.

YOUR PLATFORMCustomer sign-in · JWKSPublic toolsAccount toolsYour MCP server · your dataBUSYMATE AIKnows who’s askingAnswers for anyoneActs for one customerAssistant brain · branded chatIDENTITYlaunch token · ES256 · verified via your JWKSopen to every visitor — no token neededACTIONsigned call token · scoped to one customer

Identity — your sign-in vouches for the customer

When a customer signs in on your site, you mint a short-lived launch token (ES256). Busymate AI verifies it against your public JWKS — so the assistant knows exactly who it’s talking to, and you never hand over a shared secret.

Action — every call proves who it’s for

When the assistant calls one of your account tools, it presents a short-lived signed token your MCP server verifies — bound to that exact customer (sub) and to your connector. Your server checks the signature and serves only that customer’s data.

Anonymous visitors only ever reach your public tools — account tools stay out of reach without a verified customer.

What you build

One MCP server, two kinds of tools

You expose a single MCP server. Public tools answer anyone; account tools each receive the verified customer id and answer for exactly one person. Two small endpoints complete the setup: a public JWKS and a sign-in handoff.

Public tools

Answerable to anyone — no identity required.

  • list_plansProducts & pricing
  • faq_searchFAQ & how-tos
  • service_statusService status

Account tools

Each call scoped to the verified customer.

  • my_devicesMy devices
  • my_earningsMy earnings
  • update_profileMy profile — updates confirmed firstConfirm

Start from the kit, not from scratch

We provide a drop-in starter kit — plain Node, zero external dependencies. The tools, the JWKS endpoint, and the sign-in handoff are scaffolded; you fill in the stubs against your own data.

Go live

Four steps to your own assistant

  1. Implement your tools

    Take the starter kit and wire the stubs to your data — public tools first, then the account tools you want to offer.

  2. Run the self-check

    One command exercises every tool and both trust endpoints. Green across the board means you’re ready.

  3. Send us three things

    Your MCP URL, your token issuer, and your JWKS URL.

  4. We bring it live

    We publish your connector and complete the secure trust setup together. Your branded assistant goes live on your domain.

What you get

Yours in every way that matters

Your brand, your domain

The assistant lives on your subdomain — your name, your look, and a custom host if you want one.

Help for every visitor

Product, pricing, and support answers around the clock — before anyone signs in.

Real account actions

Signed-in customers check devices, earnings, and settings in plain language.

Confirmation built in

Sensitive actions pause for an explicit yes from the customer before anything changes.

Data under your control

Every answer comes from your tools on your servers. Nothing is copied into ours.

Proven in production

The exact integration in this guide runs live today with our first white-label partner.

Next step

Ready to integrate?

Tell us about your product and we’ll walk the trust setup with you — from starter kit to a live branded assistant on your own domain.

Talk to us at Busymate AI

Busymate AI · White-Label Integration

Product examples are illustrative.