Muse connector documentation
AI Website Builder and Digital Marketing + SEO
Two Model Context Protocol connectors from Dance for small-business owners. AI Website Builder builds and manages the website. Digital Marketing + SEO finds the change that wins more customers and makes it.
Start with the section for the connector you’re using or reviewing. Everything after those two sections applies to both: they run on the same Dance service, so one access key, one account and one change history work on either.
Built by Dance Technologies, Inc. Support: admin@startdancing.ai. Not affiliated with or endorsed by Meta; listing in Muse is subject to Meta’s review.
Connector
AI Website Builder by Dance
Build, redesign and manage your business website with AI.
Use when someone wants to create, rebuild, redesign, edit, publish or check on their business website, for example a new site, a modern redesign, adding a page, changing the text on a page, or putting it on their own domain.
| Item | Value |
|---|---|
| Endpoint | https://www.startdancing.ai/muse/mcp/website |
| Server name | dance-website-builder |
| Landing page | https://www.startdancing.ai/muse/website-builder-connector |
| Authentication | None needed to start. Tools that act on your own websites ask you to sign in to your Dance account (OAuth 2.1 with PKCE); an operator-issued Dance access key still works as a Bearer token. |
What it does
New websites: a free preview, paid to keep. build_website builds a modern website from the person’s current one on Yoink (yoink.website), a Dance product, and returns a private link where they watch it being built. The preview is free; keeping it is paid. buy_website shows the current terms in the conversation, approval first: the seller, the price and how it is billed, what it includes, how to cancel if it renews, and refunds; only after the person says yes it hands over the secure link for exactly those terms. Card details never enter the conversation. Their current website, domain and DNS are not changed. When there is no website at the address, nothing is built automatically: Dance’s team follows up to build it with them.
Websites built here: any change, then their own domain. change_website takes any change in plain words: a new page, a section, a photo from their current site or a public image link, a booking button that goes to their existing booking tool, layout or words. Each change lands on the preview first, and undo_website_change takes the latest back out. On the free preview, changes stay on the homepage; new pages come with keeping the website (buy_website). Once it is kept, publish_website shows them the preview and puts live only the version they approve; then connect_domain connects a domain the person already owns and returns the DNS records to add. Dance never sells or registers domains, and image files can’t be uploaded from the chat.
Connected websites: text changes with approval. On a site whose owner connected a compatible CMS, it changes page text (see What can be edited): it plans the exact before and after, saves an unpublished draft, publishes only after the person approves, checks the live page, and can undo that one change.
Tools it leads with (19)
Both Dance connectors list every Dance tool and share one account, so nobody needs to install the other one. These are the tools this connector is focused on.
- sign_inRead
- list_my_websitesRead
- build_websiteWrite
- get_website_buildRead
- find_my_websiteWrite
- buy_websiteSensitive write
- change_websiteWrite
- get_website_change_statusRead
- undo_website_changeWrite
- publish_websiteWrite
- connect_domainWrite
- check_domainRead
- list_connected_sitesRead
- get_site_contextRead
- prepare_website_changeWrite
- apply_website_changeWrite
- publish_website_changeSensitive write
- get_website_changeRead
- revert_website_changeSensitive write
Try it as a reviewer
- Add
https://www.startdancing.ai/muse/mcp/websiteas a connector, with the reviewer key as a Bearer token (or no key, as a guest). - “Build me a new website. My current one is polarseltzer.com.” It returns a private link right away; the preview is ready in a few minutes. This is a real build and uses the key’s one new preview a day.
- “Is my new website ready?” Once it is: “Make the headline on my new website shorter.” The change lands on the preview. “Undo that change” takes it back out.
- “Put my new website on polarseltzer.com.” On a preview not yet kept this explains that a domain can be connected once the website is kept, and that Dance doesn’t sell domains.
- “What websites can you edit for me?” shows the Polar demonstration site. Then “Change the headline on the lemon page to ‘Lemon Sparkling Water’.” Review the plan and the draft preview.
- Approve the publication when Muse asks, then “Is it live yet?” to see the live-page check. “Undo that change” restores the earlier text; approve it when asked.
- Ask to edit any other website, for example https://example.com, to see the connection requirement.
Example prompts
- Build a website for my business where customers can book a call.
- Give my current website a fresh look.
- Add a page for our new service and match the rest of my site.
- Add a “Book now” button that goes to my Square page.
- Move the reviews above the services.
- Put my new website on mybusiness.com. I already own it.
- Change my homepage headline to “Family-Owned Since 1984”.
- What websites can you edit for me?
- Publish it.
- Undo that change.
Connector
Digital Marketing + SEO by Dance
Digital marketing and SEO for small businesses: find the change that matters most, then make it.
Use when someone wants more customers or more visibility online: SEO audits, Google rankings, search demand and keywords, who outranks them, what to change on their website first, and making that improvement.
| Item | Value |
|---|---|
| Endpoint | https://www.startdancing.ai/muse/mcp/marketing |
| Server name | dance-marketing-seo |
| Landing page | https://www.startdancing.ai/muse/digital-marketing-seo-connector |
| Authentication | None needed to start. Tools that act on your own websites ask you to sign in to your Dance account (OAuth 2.1 with PKCE); an operator-issued Dance access key still works as a Bearer token. |
What it does
Any public website: research and recommendations. analyze_business reads the site, Google search demand and results, and AI answers (whether Google AI Overviews and ChatGPT cite the business, and who they cite instead). It ranks what to fix first, with the evidence behind each point. With propose_page_update the assistant drafts the exact before and after from Dance’s rules and that evidence, and Dance checks every claim before saving it. It never changes a website it has only analyzed.
Connected websites: making the change. When the site’s owner has connected a compatible CMS, the recommendation becomes a change: an exact plan, an unpublished draft, publication only after the person approves, a check of the live page, and an undo. Anywhere else, the person gets the exact change to make.
The first supported CMS is Dance’s structured CMS. Dance does not edit arbitrary WordPress, Wix or Squarespace sites and takes no payments itself.
Tools it leads with (15)
Both Dance connectors list every Dance tool and share one account, so nobody needs to install the other one. These are the tools this connector is focused on.
- sign_inRead
- list_my_websitesRead
- analyze_businessWrite
- get_analysisRead
- propose_page_updateWrite
- plan_site_rebuildRead
- get_report_allowanceRead
- buy_reportsWrite
- list_connected_sitesRead
- get_site_contextRead
- prepare_website_changeWrite
- apply_website_changeWrite
- publish_website_changeSensitive write
- get_website_changeRead
- revert_website_changeSensitive write
Try it as a reviewer
- Add
https://www.startdancing.ai/muse/mcp/marketingas a connector, with the reviewer key as a Bearer token (or no key, as a guest). - “How can I make polarseltzer.com/lemon/ better?” Research runs (each call returns within about 80 seconds; longer runs continue automatically) and leads with the one change that matters, with its evidence.
- “Who shows up on Google instead of Polar Seltzer?” and “Does ChatGPT mention Polar Seltzer?” answer from the same research.
- “Put that proposal on the connected page.” Review the plan, apply it as a draft and open the preview link.
- Approve the publication when Muse asks, then “Is it live yet?” to see the live-page check. “Undo that change” restores the earlier text; approve it when asked.
- Ask to edit https://example.com: analysis still works, and the edit returns the connection requirement.
Example prompts
- Look at my website. What should I fix first to get more customers?
- Why are my competitors showing up on Google ahead of me?
- Help my business get recommended by AI assistants.
- Why don’t I rank for “emergency plumber Chicago”?
- Rewrite my homepage title and description.
- Make that change.
- How many free reports do I have left?
Both connectors
Everything below applies to both. Each connector lists only the tools for its job, with its own name, description and instructions, so an assistant can tell which one fits a request. Editing a connected website is in both, because both may need it, and both call the same editing and approval service.
Endpoint and authentication
| Item | Value |
|---|---|
| Endpoints | https://www.startdancing.ai/muse/mcp/website (AI Website Builder), https://www.startdancing.ai/muse/mcp/marketing (Digital Marketing + SEO) |
| Transport | MCP Streamable HTTP (POST, JSON responses). The server returns a signed Mcp-Session-Id on initialize; clients send it back so a conversation keeps one identity. |
| Protocol versions | 2025-11-25 (latest), 2025-06-18, 2025-03-26 and 2024-11-05 |
| Authentication | None needed to start. Without a key, each connection is a guest with its own free daily allowance. An optional Dance access key (Authorization: Bearer <key>) reaches an account with connected websites and higher limits; the same key works on both connectors. |
| Guests | All tools are listed and callable. Guest research on public websites is shared between guests (read-only) for 14 days, so the same site answers instantly. A wrong or revoked key is treated as a guest, never an error. |
| Server names | dance-website-builder, dance-marketing-seo (the original endpoint is muse-marketer; earlier installs named matt-mcp keep working) |
Access keys are optional and issued by Dance, for businesses that connect their website or need more than the free allowance. Each key is its own account: its investigations, proposals, connected sites and website changes are invisible to every other key, even to callers who know an ID. Only a SHA-256 fingerprint of each key is stored, and a key can be revoked at any time, which immediately stops it and disconnects its sites.
Each key carries scopes:
| Scope | Allows |
|---|---|
| research | Saved research, analysis results, page proposals and rebuild assessments. |
| live | Starting new live investigations and new website previews, within the daily limits. |
| sites | Reading and changing websites connected to this key’s account, within each connection’s own permissions. |
The original endpoint, https://www.startdancing.ai/muse/mcp (“Dance: AI Website Builder + Digital Marketing + SEO”), keeps serving every tool so earlier installs, including ones named muse-marketer or matt-mcp, keep working. New installs should use one of the two endpoints above.
curl -s https://www.startdancing.ai/muse/mcp/website \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Connected websites
A site connection links one account to one CMS deployment. It records the managed site address, the public research domain it represents, the permissions granted (read, draft, publish, revert), a sealed copy of the CMS’s own integration key, and its status. The CMS key is encrypted at rest (AES-256-GCM), is never returned by any tool or page, and is deleted when the connection is revoked.
Authorization is checked twice. The CMS verifies its integration key, that key’s permissions and the records it may touch. Dance separately verifies that the caller owns the connection and that the connection grants the action. A matching domain never grants access: it only helps find a page, and a page addressed by its research URL must be recorded in the CMS as the import of that URL.
Demonstration site. polar-website-migration.vercel.app is Dance’s demonstration import of polarseltzer.com into the structured CMS. polarseltzer.com is the research source only and is never modified. The demonstration keeps its own indexing settings (it is not indexed).
Connecting a site
- The site owner signs in to their CMS editor and opens Integrations, creates a connection key, chooses its permissions and, optionally, the pages it may touch. The key is shown once.
- The owner gives that key to Dance through a secure channel (never in a chat or a URL). Dance links it to the owner’s Dance access key and runs a connection test, which records the permissions the CMS actually grants.
- The site now appears in
list_connected_sites. Either side can revoke the connection at any time.
Asking to edit a website that is not connected returns the setup steps instead of an edit. Analysis still works.
Tools
Classifications follow Muse’s connector guidelines. Read changes nothing. Write saves data in Dance or an unpublished CMS draft. Sensitive write changes the live public website and needs approval every time.
- Write
analyze_business
On every Dance connector · focus of Digital Marketing + SEO
Researches a public website: the business, its pages, search demand, search results and AI answers, then ranks what to fix first and drafts a page proposal.
- Side effects
- Saves an investigation to the caller’s account. Reads public pages (bounded, honours robots.txt) and makes paid search-data lookups for new live investigations. A new investigation is a Dance report: it reserves one of the Dance account’s reports before starting, uses it when the report is saved (complete or partial) and gives it back if the run fails. Reusing research uses none. Never changes any website.
- Inputs
- url (homepage or deep page), goal, evidence_mode ("saved" | "live"), run_id to resume, request_id (a report kept through sign-in, payment or confirmation), confirm_new_report, country_location_code, language_code.
- Returns
- run_id, status (queued, running, complete, partial, failed, needs_input, or sign_in_needed, confirm_new_report, reports_used, reports_busy, sign_in_unavailable), stages, recommendation, proposal handoff, limitations, an expiring report link, and report_notice when a report starts or finishes.
- Read
get_report_allowance
On every Dance connector · focus of Digital Marketing + SEO
The Dance account behind the conversation: whether it is signed in, full reports left (free, bought, included with the Dance plan), its reports with links, a report waiting to continue, and payment status.
- Side effects
- None for the account. When the conversation isn’t signed in, it returns a one-time sign-in link (30 minutes) on www.startdancing.ai.
- Inputs
- None.
- Returns
- signed_in, reports (remaining by kind), your_reports (with deliverable links), waiting_report, payment.state, can_buy_reports, upgrade_url; or a sign-in link and match code.
- Write
buy_reports
On every Dance connector · focus of Digital Marketing + SEO
More full reports after the free ones: first the terms (reports in the pack and its price, read from Dance’s Stripe account; one-time, not a subscription), then, once the person approves that price, Stripe’s secure checkout link.
- Side effects
- Creates a Stripe Checkout session only after approval; charges nothing itself and never charges a saved card. Reports are added only when Stripe confirms the payment, once per payment.
- Inputs
- approved_price (the exact price shown in the terms), request_id (the report to continue).
- Returns
- state (needs_approval, checkout_ready, price_changed, not_available, sign_in_needed), terms, checkout_url, upgrade_url.
- Read
get_analysis
On every Dance connector · focus of Digital Marketing + SEO
Returns one of the caller’s investigations (or a public demo): ranked actions with evidence, confidence, sources and proposals.
- Side effects
- None. Reading never advances or changes an investigation.
- Inputs
- run_id.
- Returns
- The full analysis with evidence IDs and expiring read-only links.
- Write
propose_page_update
On every Dance connector · focus of Digital Marketing + SEO
An evidence-grounded proposal for one inspected page, written by the assistant: it returns Dance’s writing rules, the page’s content and its evidence, then checks the draft or revision the assistant sends back against that evidence and saves it.
- Side effects
- Saves a proposal revision in Dance once it passes the checks; changing shared demo material creates the caller’s private copy. Asking for the brief saves nothing. Never changes any website.
- Inputs
- run_id, action_id, page_url, instructions, draft or revision (what the assistant wrote), proposal_revision (rejects edits to a stale revision).
- Returns
- The brief to write from, or the saved proposal: ID, revision, validation checks, declined claims. A refused draft or revision returns what to fix.
- Read
plan_site_rebuild
On every Dance connector · focus of Digital Marketing + SEO
Assesses whether a finished investigation’s site would benefit from a structured, plain-language-editable CMS and returns a brief when it would.
- Side effects
- May fetch the site’s homepage once to detect its platform (cached). Builds, deploys and changes nothing.
- Inputs
- run_id, force.
- Returns
- Fit, reasons, blockers, cautions and an optional brief. The brief is not a built website; build_website builds one.
- Write
build_website
On every Dance connector · focus of AI Website Builder
Builds a brand-new website for a business from its current site, as a free homepage preview. Built and hosted by Yoink (yoink.website), a Dance product. Keeping it is paid, on the terms buy_website shows.
- Side effects
- Starts one preview build on Yoink and returns a private link to it. Never changes the current website, its domain or DNS. Charges nothing. The same site from the same account (a guest conversation or an access key) returns the same website instead of a second build.
- Inputs
- website_url (the business’s current website), email (optional; Yoink emails when the preview is ready, and it lets them find the website again from a later conversation with find_my_website).
- Returns
- website_id, status (building, ready, failed, no_website), open_url (private), price, paid.
- Read
get_website_build
On every Dance connector · focus of AI Website Builder
Reports the progress of a website started with build_website.
- Side effects
- None.
- Inputs
- website_id.
- Returns
- Status, the private link, Yoink’s live price and whether it has been kept.
- Write
find_my_website
On every Dance connector · focus of AI Website Builder
Brings back a website started in an earlier conversation, by proving the email address it was built for.
- Side effects
- With an email only: Yoink emails that address a 6-digit code (10 minutes, one use), only when it started a website here; the answer is the same either way. With the code: this conversation gets the same access to those websites as the one that built them. Never changes a website.
- Inputs
- email (the address given when the website was built), code (optional; the 6 digits from the email).
- Returns
- status (code_sent, found, none) and, once found, each website’s website_id, status, private open_url, Yoink’s live price and whether it has been kept.
- Sensitive write
buy_website
On every Dance connector · focus of AI Website Builder
Buys a website started with build_website, in the conversation, approval first. Without approved_price it returns only the terms: Yoink's live offer, a one-time purchase from Yoink or a Dance membership, with the seller, the price and how it is billed, what it includes, how to cancel if it renews, refunds and the full terms. With the amount the person approved, and the terms' version when they give one, it returns the secure link for exactly those terms: Stripe's checkout, or Dance's own page to start a plan.
- Side effects
- Hands over one secure link, only after the person approved the terms shown: for a one-time purchase, Stripe Checkout on Yoink (Link works), payment confirmed by Stripe’s webhook to Yoink; for a Dance membership, Dance’s own page, where the person picks a plan and adds a card, the start confirmed by Dance to Yoink. The person pays or adds a card there, never in the chat, and the connector never sees card details. Refuses with price_changed if the amount due, or a membership’s terms, differ from the approved ones. Repeating returns the same link, never a second charge.
- Inputs
- website_id, approved_price and approved_terms (only after the person approved).
- Returns
- state (needs_approval, checkout_ready, confirming, paid, kept), offer, a membership’s terms with their terms_version, amount_due, checkout_url (only once approved), purchase (amount paid, receipt, order) once paid, editor_url once kept.
- Write
change_website
On every Dance connector · focus of AI Website Builder
Sends a plain-language change (a page, section, photo from their site or a public image link, booking button, layout, words) to the builder of a website started with build_website.
- Side effects
- Changes the website’s preview only, never the live site. On the free preview, changes stay on the homepage and each one uses a free change; a refused or failed change uses none.
- Inputs
- website_id, request (plain words, up to 2,000 characters).
- Returns
- change_id, state (working, applied, saved, answered, refused, failed, unconfirmed), the builder’s reply, preview_url, changes_left, can_undo.
- Read
get_website_change_status
On every Dance connector · focus of AI Website Builder
Reports where one change or undo stands. Never sends it again.
- Side effects
- None for the person; a finished change is moved onto the preview.
- Inputs
- change_id.
- Returns
- The same fields as change_website.
- Write
undo_website_change
On every Dance connector · focus of AI Website Builder
Takes the latest change back out, when it is the person’s own and nothing else is running.
- Side effects
- Changes the website’s preview only.
- Inputs
- website_id.
- Returns
- change_id and its state, as change_website.
- Write
publish_website
On every Dance connector · focus of AI Website Builder
Shows what a kept website would put live (preview and version) with approval_url: the person approves that exact version on Dance’s review page, signed in to their Dance account, and it is published from there. Needs sign-in.
- Side effects
- None from the conversation: only the review page publishes, and only the approved version. Nothing is published if the website changed after the person looked. Never touches a connected website.
- Inputs
- website_id.
- Returns
- state (not_published, publishing, live), live_url, version, preview_url, approval_url, up_to_date.
- Write
connect_domain
On every Dance connector · focus of AI Website Builder
Connects a domain the person already owns to a website started with build_website, once it is kept and published (publish_website), and returns the exact DNS records to add where its DNS is managed.
- Side effects
- Attaches the domain to the website’s hosting. Never changes the person’s DNS, and never buys, registers or transfers a domain.
- Inputs
- website_id, domain.
- Returns
- status (needs_verification, pending_dns, active), the DNS records to add, live_url once live over HTTPS.
- Read
check_domain
On every Dance connector · focus of AI Website Builder
Re-checks a connected domain: live yet, or which records are still missing.
- Side effects
- None.
- Inputs
- website_id, domain.
- Returns
- The same fields as connect_domain.
- Read
sign_in
On every Dance connector · focus of AI Website Builder and Digital Marketing + SEO
Signs the person in to their Dance account (in apps that can connect accounts, it opens Dance’s sign-in) and says which account is connected.
- Side effects
- None. Signing in keeps websites, research, changes and free reports with the account in every conversation and app.
- Inputs
- None.
- Returns
- status (signed_in, access_key, operator), email, number of websites.
- Read
list_my_websites
On every Dance connector · focus of AI Website Builder and Digital Marketing + SEO
Lists every website the signed-in person can work on, for them to choose from: sites connected for editing, websites built here, and websites in their Dance account. Needs sign-in.
- Side effects
- None.
- Inputs
- None.
- Returns
- Websites with the id each tool takes (site_id, website_id or url), and recent website changes.
- Read
list_connected_sites
On every Dance connector · focus of AI Website Builder and Digital Marketing + SEO
Lists the websites connected to the caller’s account, with their permissions and capabilities.
- Side effects
- None.
- Inputs
- None.
- Returns
- Sites (managed address, research domains it represents, permissions, status) or the setup steps when none are connected.
- Read
get_site_context
On every Dance connector · focus of AI Website Builder and Digital Marketing + SEO
Finds a page on a connected site by URL, path, record ID or search, and returns its published values, editable fields, any draft and its version.
- Side effects
- Reads from the connected CMS. Changes nothing.
- Inputs
- site_id, page, query.
- Returns
- Page record with editable fields and limits, unsupported areas, open changes.
- Write
prepare_website_change
On every Dance connector · focus of AI Website Builder and Digital Marketing + SEO
Reads the page’s current content from the CMS and saves a validated change plan with the exact before and after of every field. Accepts explicit field values, a plain-language request, or a proposal.
- Side effects
- Saves a plan in Dance. Changes nothing in the CMS or on the website. Plain-language requests are mapped by the AI model; no crawl or keyword research runs.
- Inputs
- site_id, page, changes[] or request or proposal_id (+ proposal_revision), context, change_id (revise), idempotency_key.
- Returns
- change_id, plan_revision, plan_hash, changes (before → after), not_applied, approval_summary.
- Write
apply_website_change
On every Dance connector · focus of AI Website Builder and Digital Marketing + SEO
Saves exactly one plan revision to the connected CMS as an unpublished draft, then reads it back.
- Side effects
- Creates one draft change in the CMS. Nothing is live. Creates a signed draft-preview link that expires after two hours. Refuses if the page changed or holds someone else’s draft.
- Inputs
- change_id, plan_hash, idempotency_key.
- Returns
- CMS change reference, baseline and draft versions, read-back result, preview_url.
- Sensitive write
publish_website_change
On every Dance connector · focus of AI Website Builder and Digital Marketing + SEO
Publishes only this change’s own draft to the live website, then fetches the public page to verify the new values.
- Side effects
- Changes the live public website. Other pending drafts are never published. Fails without changing anything if the plan, draft or page changed after approval.
- Inputs
- change_id, plan_hash (the plan the person approved), idempotency_key.
- Returns
- Publication reference and version, verification (verified, pending or mismatch) or approval_url.
- Read
get_website_change
On every Dance connector · focus of AI Website Builder and Digital Marketing + SEO
Reports the actual state of one change, or lists recent changes.
- Side effects
- Asks the CMS about any unconfirmed operation and re-checks the public page, then records what it found. It never repeats or starts a write.
- Inputs
- change_id (optional).
- Returns
- Status, CMS references, versions, verification and next step.
- Sensitive write
revert_website_change
On every Dance connector · focus of AI Website Builder and Digital Marketing + SEO
Undoes exactly this change: removes its draft, or restores the live page values from before it was published.
- Side effects
- Changes the live public website when the change was published. Never undoes an unrelated change. Refuses if the page was edited since.
- Inputs
- change_id, plan_hash, idempotency_key.
- Returns
- Reverted CMS references, read-back of the restored values and public-page verification.
Approval and publishing
Talking about a change is not permission to make it, and a draft is not permission to publish. The flow is: prepare_website_change (plan) �� apply_website_change (unpublished draft, read back from the CMS) → publish_website_change (live, verified) → optionally revert_website_change.
Every plan has a plan_hash that pins its exact fields, values, page and the CMS version it was read from. Revising a plan creates a new revision and a new hash, and approval given for the old one no longer works, in either direction. If the page changed in the CMS after the plan was read, or holds someone else’s unpublished draft, nothing is written.
In Muse. publish_website_change and revert_website_change are sensitive writes, so Muse asks the person to Allow once or Deny every time, showing the change and its approval_summary. The access key issued for Muse treats that allowed call as the approval for exactly the change_id and plan_hash shown. Dance does not use or imitate any other Muse approval interface.
Other MCP clients. For keys whose client cannot guarantee a per-use human approval, publishing and live reverts return an approval_url instead. That Dance review page shows the exact before and after; the person approves by entering their own access key. The link expires after 24 hours and is tied to the change, the action and the plan hash. A value supplied by the model, such as an “approved” flag, is never accepted as approval.
Publication affects only the change’s own records. Other pending drafts on the site, including other editors’ work, stay unpublished. Reverting undoes only the identified change and refuses if the page was edited since.
Status, retries and errors
| Status | Meaning |
|---|---|
| planned | A plan exists in Dance. Nothing in the CMS. |
| drafted | Saved as an unpublished draft in the CMS and read back. Nothing is live. |
| awaiting_approval | Publication requested; waiting for the person to approve on the review page. |
| published | The CMS confirmed publication. See verification for what the public page shows. |
| reverted | This change was undone. The page fields are back to their earlier values. |
| conflict | The page changed outside this plan, so nothing was overwritten. Prepare a new plan. |
| failed | The operation failed without modifying the site. See last_error. |
| applying · publishing · reverting | An operation started and its result is not yet confirmed. get_website_change reconciles it with the CMS. |
Verification. After publishing or a live revert, Dance fetches the managed public page without caches and checks the title, meta description, H1 and changed copy. verified means the page shows every value. pending means the CMS confirmed the change but the page could not be read or still shows older content; it is reported as propagating, not as failed. get_website_change checks again.
Retries. Write tools accept an optional idempotency_key. Repeating a call with the same key and request returns the stored result without writing again; reusing a key for a different request fails without changing anything. Applying, publishing or reverting the same plan revision twice also writes nothing new, and every CMS mutation carries its own idempotency key that the CMS records in the same transaction as the content change. If a call times out, the outcome is reported as uncertain: call get_website_change, which asks the CMS what happened instead of repeating the action.
| Error | Meaning |
|---|---|
| needs_input | No website or page was given. Nothing was started; ask the person which site they mean. |
| no_connected_site · site_not_connected | The website is not connected to this account. It can be analyzed, not edited. Setup steps are included. |
| permission_denied | The access key or the site connection does not allow this action. |
| identity_unverified | The managed page is not recorded as the import of the research URL given. Name the managed page directly. |
| unrelated_draft | The page already holds someone else’s unpublished draft. The connector will not merge into or publish it. |
| conflict | The page changed after the plan was read. Nothing was written. |
| plan_changed | The plan_hash is not the current plan revision. Review and approve the current plan. |
| validation_failed | A requested value is not allowed (unknown field, too long, markup, unknown link). Nothing was planned. |
| idempotency_key_reused | That idempotency_key was used for a different request. Nothing was changed. |
| request_in_progress | The same request is running or its outcome is unknown. Check get_website_change. |
| cms_unreachable · outcome "uncertain" | The CMS did not confirm. Nothing is assumed; get_website_change asks the CMS what happened. |
| daily_limit | A published usage limit was reached. Saved research still works. |
| unsafe_url | The address is not a public website (private networks and unsafe redirects are refused). |
| invalid_address | build_website: not a public address. Nothing was built. (An address with no website returns status no_website: Dance’s team follows up in person.) |
| unavailable | Website tools: Yoink did not answer. Nothing was built or charged; a change already sent is read back with get_website_change_status, never resent. |
| code_invalid · code_expired · too_many · invalid_email | find_my_website: the 6-digit code is wrong, older than 10 minutes, or tried too often, or the email isn’t an address. Nothing was opened; ask for the code again or send a new one. |
| not_paid · not_published | connect_domain: the website must be kept (buy_website), then published once (publish_website), before a domain connects. publish_website: not_paid = keep it first. Nothing was connected or published. |
| price_changed | buy_website: the amount due is no longer the amount the person approved. No link was given and nothing was charged; show the current terms and ask again. |
| kept_on_dance | change_website, undo_website_change: the website was kept with a Dance membership, so its changes are made in its Dance editor (buy_website returns editor_url). Nothing changed. |
| not_ready | buy_website: the website is still being built; it can be kept once get_website_build says ready. Nothing was charged. |
| invalid_domain | connect_domain / check_domain: not a domain name that can be connected. Nothing was connected. |
| site_unreachable | No server answers for that address (DNS lookup failed). Nothing was analyzed; confirm the address and try again. |
| sign_in_needed | analyze_business: a new report needs a free Dance account (1 free report included). Nothing was started or used; the request is kept, and request_id continues it after signing in. |
| confirm_new_report | analyze_business: the account already has a report for this site, so a fresh analysis would use another. Nothing was started; continue with request_id and confirm_new_report only if the person agrees. |
| reports_used | analyze_business: no reports left. Nothing was started or charged; buy_reports or a Dance plan upgrade continues it (request_id). Existing reports stay available. |
| reports_busy | analyze_business: today’s free reports across Dance are used up; new free reports open tomorrow. Bought and plan reports are unaffected. |
What can be edited
On a connected page, one change can update any of these existing fields:
- SEO title and meta description
- Page headline (H1)
- Introduction or hero paragraph
- Tagline on product pages
- Labels and destinations of existing buttons (a page on the same site, or a link the site already uses)
- Text of existing sections: headings, eyebrows, subheadings, paragraphs, bullets, intros and bodies
Not supported:
- Images, layout, adding or removing sections, creating or deleting pages
- Navigation, footer and other sitewide settings (no sitewide changes are possible through the connector)
- Prices, product facts, nutrition and structured data
- Any website that is not connected through a compatible CMS, including arbitrary WordPress, Wix or Squarespace sites
Values must be plain text within each field’s limit, and links must point to an existing page on the same site or a link the site already uses. When a recommendation includes something the CMS cannot apply, such as a new section or FAQ, it is listed under not_applied in the plan before anything runs, so nothing is silently dropped. On product pages the H1 is stored separately from the product name, so changing a headline does not rename catalog cards or breadcrumbs.
Usage limits
Using the connector is free within these limits. One thing it leads to is paid: a website built with build_website is a free preview, and keeping it is paid, on the terms buy_website shows in the conversation for the person's approval, or on yoink.website. The connector never sees card details.
| What | Limit |
|---|---|
| Full reports (new investigations) | Each Dance account includes 1 free report, once, shared across both connectors and every conversation signed in to it; then bought reports or what the Dance plan includes. A report counts only when it is saved; failed runs give it back. Free reports across Dance are capped at 100 a day. Without a Dance account a guest can still reuse research already done for a public site (shared with other guests), which uses no report. Access keys not signed in to an account keep their own daily limits (3 a day by default, 5 for the reviewer key, 6 a day per network, 30 a day across keys). Reusing finished research, reading or downloading reports and all planning advice are never limited. |
| Website-change operations | 60 a day per account and 120 a day per network (prepare, apply, publish and revert each count). |
| New website previews | 1 a day per account (guest conversation or access key), 2 a day per network for keys and 5 for guests, and 10 a day across Dance. Checking a website already started is not limited. An address with no website builds nothing and uses none. |
| Changes to websites built here | 20 a day per account, 40 a day per network and 200 a day across Dance (changes and undos), on top of the website’s own allowance on Yoink: a few free changes on the preview, homepage only, then the kept website’s allowance. Checking a change is not limited. |
| Crawling | Up to 60 pages per investigation (7 for a single deep page), public addresses only, robots.txt and its crawl delay honoured, at least 2 seconds between requests to one site. |
| Call duration | Each call returns within about 80 seconds. When a data provider is slow, the step in progress is still finished and saved even if the call itself times out; calling again with the run_id continues from there. Longer investigations return status "running" and a run_id to continue. |
| Field lengths | SEO title 120 characters, meta description 320, H1 140, introduction 1,500, button label 60. Plain text only. |
| Scope of one change | One page and up to 20 fields per change. |
| Links | Report and proposal links expire after 7 days and can be revoked; draft previews after 2 hours; approval links after 24 hours. |
| Reports missing parts | A report missing parts because a data provider failed on its side never uses a report. One missing parts because Dance couldn’t finish a step of its own doesn’t either, once a day per account; after that it is used, and the person is told. One missing parts because of the website, or because a request was refused as invalid, does use a report. |
Data handling
What is stored, per account: the websites a person asks about and the evidence gathered from them (page text excerpts, search data), investigations, proposals and their revisions, change plans with their before and after values, CMS change references, approval records and verification results. Access keys are stored only as fingerprints; connected-site credentials are encrypted.
Who processes it: Vercel (hosting and the AI Gateway, which sends prompts to the configured model provider, currently Anthropic), Neon (database, United States) and DataForSEO (search data and AI-answer visibility for the domains and keywords being researched). For a new website, Yoink (Dance) receives the current site’s address, an opaque ID for the access key (never the key) and, only if the person gives it, an email address for the ready notice. Changes go only to the CMS the site owner connected. Dance’s private analytics accounts are never exposed to other callers.
Use: only to answer the person’s requests and to operate, secure and support the connector. Data shared through Muse is not sold, not used for advertising or unrelated profiles, and not used to train models.
Retention and deletion: guest research on public websites is kept 14 days. An account’s research and change history are kept while its access key is active, and deleted or made inaccessible within 30 days of the key being revoked or a deletion request (privacy@startdancing.ai), except change records kept for security or legal reasons. Revoking a site connection deletes its stored CMS credential immediately. Report links, draft previews and approval links expire.
Safety: fetched website content is treated as evidence and never as instructions; it cannot authorize an edit or change permissions. Crawling is bounded, honours robots.txt and refuses private network addresses. Secrets never appear in tool output, URLs or logs.
The connector privacy notice and connector terms apply, alongside Dance Technologies’ general Privacy Policy and Terms of Use.
Reviewer key
Reviewers receive a dedicated access key through the submission portal’s secure credential method. It is never published and works on both endpoints; the step-by-step paths are under AI Website Builder and Digital Marketing + SEO. The key:
- Has its own isolated account with research, live and sites scopes, and 5 new live investigations a day.
- Uses Muse’s per-use approval for publishing and reverting (sensitive writes).
- Is connected to the Polar demonstration site with read, draft, publish and revert permission on a fixed set of test pages, including /lemon/. It cannot touch sitewide settings or other pages.
- Can be revoked by Dance at any time; a replacement is issued on request at admin@startdancing.ai.
