# SmashOne — Connect your agent to SmashOne (v9)

CONNECT YOUR AGENT TO SMASHONE
This file tells an AI assistant how to connect itself — or guide its user to
connect it — to SmashOne, so the assistant can work with the account directly
instead of only advising. One address does the whole thing; the client calls it
a custom connector, a custom app or a plugin, depending on which one you are.

WHAT THE CONNECTION GIVES
Once connected through OAuth, the assistant can read the user's SmashOne
workspace and, when the user grants write access, act through approved intent
doors. The 13 doors cover overview, business details, staff and setup, channels,
catalog, support, publications, bookings, customers and conversations, money,
the client partner program, and bounded multi-business status. Paying (a Stripe
checkout on the SmashOne site) and provider sign-in always stay with the human;
the assistant never spends the user's money.
The support door also reads and sets the owner's escalation channels and sends a
test notification. Workspace and email stay on; optional direct messages are
limited by the server to Telegram, Facebook and Instagram. WhatsApp cannot be an
owner escalation recipient. The link that binds a direct-message recipient is a
credential, so it is handed out only with write access, never by a read.
Before hiring an address-dependent role, read the business profile. If the staff
door returns service_address_required, collect and save the complete US service
address through the existing business profile action, then retry the hire.

PLAN AVAILABILITY
Connection availability depends on the provider and the customer's plan. Check the provider's current rules; do not promise that a particular plan will work.

THE ADDRESS
SmashOne connection address: https://api.smashone.us/mcp
Transport: Streamable HTTP (POST). Sign-in: standard OAuth — the connector
sends the user to the SmashOne sign-in page; the user logs in with their
workspace account and approves the requested access. One shared URL for
everyone; the workspace is resolved from the signed-in account. Where a client
offers a token field, a personal API token from the workspace (Settings -> API
tokens) also works as a read-only Authorization: Bearer header. Write actions
require the OAuth connector. Never let the user paste a token or password into
the chat itself.

CONNECT FROM CLAUDE (web)
Fastest path — the prefilled install link:
https://claude.ai/login?from=logout&returnTo=%2Fcustomize%2Fconnectors%3Fmodal%3Dadd-custom-connector%26connectorName%3DSmashOne%26connectorUrl%3Dhttps%253A%252F%252Fapi.smashone.us%252Fmcp
The user opens the link, signs in to Claude if asked, and sees the "Add custom
connector" dialog with the name and URL already filled in. A red note saying
the connector "was suggested by an external link" is Claude's standard notice,
not an error. Press Add, then open the connector card and press Connect — a
SmashOne sign-in window appears; log in and approve. Manual path: Settings ->
Connectors -> Add custom connector -> paste https://api.smashone.us/mcp -> Add. In a chat,
press "+" and enable the SmashOne connector for that conversation.

CONNECT FROM CHATGPT (New Plugin)
ChatGPT: open Settings, then Plugins, turn on Developer mode, add a plugin with the address https://api.smashone.us/mcp and sign in.
Authentication: OAuth. OAuth settings are discovered from the address; nothing else to paste. The ELEVATED RISK badge is ChatGPT's
standard wording for all unverified connectors.
If the Developer mode toggle is absent (plan or workspace policy), say so
honestly and guide the user by this pack instead.

CONNECT FROM THE GEMINI APP (Gemini Spark)
Requirements Google enforces for custom apps: a personal Google account, not a work or school one, a Google AI Pro or Ultra subscription — that is what opens Spark in the US, the United States, and age 18 or over, “Keep Activity” switched on, a computer: custom apps can only be added in the web app, not on the phone, English — custom connected apps are available in that language only.
1. On a computer, gemini.google.com -> Settings & help -> Connected Apps. Custom
   apps can only be added in the web app; a phone will not show the option. If
   the item is missing, activate Gemini Spark first (Spark onboarding appears
   once) and return here.
2. Choose "Add a custom app" -> paste https://api.smashone.us/mcp -> Next.
3. Review the consent screen and press Connect, then complete the SmashOne
   sign-in. Once connected, the app works in both the web and the mobile Gemini
   app. In a chat, call it by typing @SmashOne.

IF THE CONNECTION FAILS
Do not retry in a loop. Say plainly which step failed, and continue guiding
the user by the onboarding file of this pack (/llm/onboarding.txt) — every
setup step can also be done by hand in the workspace at app.smashone.us.
Support: https://smashone.us/support/

WHAT NOT TO DO
Do not invent tools that the server does not expose. Do not promise actions
outside the granted scopes. Never ask the user to paste their SmashOne
password into the chat — sign-in happens on the SmashOne page only.

SEE IT WORKING BEFORE YOU BUY
Two sample businesses are run day to day by AI employees:
- Tampa Pasta House — an illustrative family restaurant in Tampa, Florida.
- Casa Lista Home Repair — an illustrative handyman business serving customers
  in English and Spanish, with a live phone line.
Try both through the messenger doors on the homepage at https://smashone.us.
These are sample businesses for illustration, not real SmashOne customers.

Source of truth: https://smashone.us — if this file conflicts with the live site, the site wins.