गाइड
एम्बेड को Code Block/Embed Block (या Business+ पर Code Injection) के ज़रिए वायर करें, इसे अपने पेज सीखने दें, एक सदस्य को अपने पहचाने गए विज़िटर के रूप में रजिस्टर करें, और WebMCP से पेज ऐक्शन जोड़ें।
Squarespace has no plugin runtime, so Busymate AI reaches a Squarespace site through the universal embed — one script tag placed via a Code Block or Embed Block inside a page. Squarespace's own Code Injection (a site-wide header/footer script, the simplest path on WordPress/Ghost/BigCommerce) is a paid-plan feature on Squarespace — it is greyed out behind an upgrade prompt on the free trial and on the entry Personal plan, so start with the block-based path below if you're not sure which plan you're on.
If your plan has Code Injection (Business or higher):
Open Settings → Advanced → Code Injection.
Paste the one script tag from your Console connection settings into Header:
<script src="https://busymate.ai/embed/v1.js" data-assistant="<your-workspace-slug>" data-label="Ask us" async></script>Save. The floating widget now appears on every page — nothing else to configure for that part.
On a plan without Code Injection:
Either way, the widget needs your site to be Public to render for a real visitor — see "Before you start" above.
Alongside the embed script, a second small script can register the page's own actions — "view the class schedule," "book a session" — through the standard document.modelContext WebMCP surface, so the assistant can act instead of only answering. Drop it in the same Code Block/Embed Block or Code Injection panel, after the embed script tag. See Add page actions with WebMCP for the shape.
Point a website source at your own Squarespace site URL — the same crawler every connection uses, reading your published pages and citing back to the page an answer came from.
Squarespace's native Member Areas feature (on Business/Commerce plans) is the identified-visitor layer: register your own site (or a small backend you control) as an identity provider — see Recognize signed-in customers for the exact fields (issuer, JWKS URL, the launch endpoint) — then define window.BusymateAI.getIdentity before the embed <script> tag (the embed captures it once at load) so a signed-in customer is recognized without asking twice. Without Member Areas, register a small backend of your own as the identity provider for a fixed set of accounts instead.
For a store or class-booking site, Busymate AI can answer from your real Commerce data — not just crawled page text — through a Squarespace Developer API key. Unlike Code Injection and Site Availability, minting this key is not plan-gated: it works on the 14-day trial.
create_app_secret MCP tool so it lands encrypted in the Vault, never in a chat log or file.GET /1.0/commerce/products only covers Physical/Digital/Gift Card products — a class/appointment Service product (Squarespace Scheduling) returns an empty list there even when real services exist. GET /1.0/commerce/inventory DOES list Service products (by SKU/descriptor/stock), so it is the practical read path for a services/classes business today. GET /1.0/commerce/orders and GET /1.0/profiles read real transactions/customers once your site has any — both are correctly empty on a fresh site.Every step above is available from any MCP client on your own account:
claude mcp add --transport http busymate-ai https://busymate.ai/mcp/embed/v1.js.getIdentity must be defined before the embed script tag runs; check it with window.BusymateAI.getIdentity() in the browser console.getIdentity bridge hands off, registered as an identity provider.Squarespace reserves site-wide Code Injection for the Business plan and above. Below that, a Code Block or Embed Block placed inside each page's own content still runs its script once the page is published — no upgrade required.
No — Site Availability gates the whole page, embed included. The widget only renders once real visitors can reach the page, i.e. once Site Availability is Public.
Only the universal embed today. A registered Squarespace Extension (OAuth app via Squarespace's developer portal) is on the roadmap for a deeper, native integration.
Not without a paid plan. Site Availability on a 14-day trial only offers Password Protected, Private, or (Enterprise) SSO Protected — "Public" shows an "Upgrade to publish" prompt instead of a selectable option. Everything else in this guide (embed placement, knowledge, WebMCP actions, a Developer API key for Commerce data) works on the trial; only real anonymous reachability needs the upgrade.
No — generating a Developer API key (Settings → Advanced → Developer Tools → Developer API Keys) works on the trial even though the generator shows a "Premium Feature" banner for Commerce scopes. That banner did not block key generation when tested. Publishing the site (Site Availability → Public) is the separate, genuinely plan-gated step.