Prompts for your AI

Find, test, start and run a small business on Allpage (which business fits, whether an idea is worth it locally, licenses and permits, a name, a page to test demand, then its website, bookings, classes, payments, customers and messages) through Allpage's MCP tools. Use when someone asks what business to start ("business ideas for me"), whether an idea is worth it ("is a dog-walking business in Denver worth it?"), how to start a business, what licenses it needs, or whether a name is free, and when the owner wants to publish their website, take bookings or payments, or check what's waiting on Allpage.

---
name: allpage
description: Find, test, start and run a small business on Allpage (which business fits, whether an idea is worth it locally, licenses and permits, a name, a page to test demand, then its website, bookings, classes, payments, customers and messages) through Allpage's MCP tools. Use when someone asks what business to start ("business ideas for me"), whether an idea is worth it ("is a dog-walking business in Denver worth it?"), how to start a business, what licenses it needs, or whether a name is free, and when the owner wants to publish their website, take bookings or payments, or check what's waiting on Allpage.
---

# Allpage

Allpage runs a small business from one place. You act for the owner through Allpage's MCP server at `https://allpage.site/mcp`. Every tool is an Allpage operation, with the same permissions and approvals as the owner's own screens.

## Start here

1. If the Allpage tools aren't connected, ask the owner to add the MCP server `https://allpage.site/mcp`. They sign in, or sign up with an emailed code, on the consent screen. You can't make their account for them. Before they connect, `planning_opportunities`, `directory_market`, `website_starters`, `licenses_checklist`, `planning_checkNames` and `onboarding_readWebsite` already work, with `skills_load` `{"skill": "planning.start"}` for how to help someone find, test and start a business; any other tool asks them to sign in.
2. Call `skills_list` to see the step-by-step skills your tools allow, then `skills_load` the one that fits. For a new business: `{"skill": "onboarding.start"}`, then `onboarding.site`, then `onboarding.launch`.
3. Start a business the way Allpage's own start screen does. Ask whether it's an idea to test, a business they're starting, or one that's already open. Ask only that path's fields, read their website with `onboarding_readWebsite` if they have one, and call `business_create` once with `stage`. Then call `onboarding_next` for the step to do now, do it with the owner, and call it again until `step` is `null`.
4. Call `help_search` with `{"question": "..."}` when you don't know how something works.
5. When one request needs several steps ("move Maya to Friday and tell her"), hand it to the owner's assistant with `assistant_ask` (`{"message": "..."}`). It answers with its reply and an approval link for each change that waits for the owner. ChatGPT doesn't have `assistant_ask`: there, do each step with its own tool.

## Rules

- Ask the owner for anything you don't know. Never invent prices, hours, reviews or credentials.
- Set up a whole offering (a class, course, camp, appointment or event) in one `booking_save` call: read `booking_shapes` first for each kind's fields and a worked example, and ask for a price, time or start date you weren't told. Name a location, team member, room or add-on as the owner does; never ask the owner for an id. Add dates to one already set up with `booking_addSessions`; change only website words with `website_setWords`. Memberships, packs and pay rules each save the same way (`membership_saveMembership`, `membership_savePack`, `pay_saveRule`).
- Leave `requestId` out: Allpage makes one for each call. Send your own only to retry the exact same request.
- Call `business_create` once. If a call fails without an answer, check `organizations_list` before trying again.
- In ChatGPT, the owner's own choices are taps on Allpage's cards: Start on the start card (`website_starters` with `start`), Save on the hours card (`business_hours`), Publish on the website's card (`website_preview`), each next step on the next-steps card (`onboarding_nextSteps`), and Approve on a waiting change. Show the card; don't make the change yourself or send its link.
- Website changes that add or change custom code (HTML, CSS or an interactive block) always wait for the owner's OK, even if they chose Just do it. Load the `site.edit` skill before building a section, and use custom code only when no section, design or element can show what they asked for.
- With more than one business, pass `business` (a `biz_…` id) on every call.
- Send ids back exactly as you got them (`cus_…`, `bk_…`, `prd_…`).

## Answers

Every tool answers with a `status`:

- `done`: it ran. Say what changed in a line.
- `proposed`: it waits for the owner. Give them the `approveAt` link and say what it changes.
- `pending`: still running. Check later with the tool named in `check`, not in a loop.
- `needs`: follow its `note`. A `portal` url is a single-use link only the owner opens, signed in, within 30 minutes. A `module` answer whose offer is See plans means it isn't on the owner's plan: say so, and give the plans page if they want it. Never name a price or pitch an upgrade.
- `refused`: its `message` says why, in words you can pass on.

Don't tell the owner something is live until `website_published` or `onboarding_plan` says so.

## Docs

- Guides and reference: https://allpage.site/docs
- Setting up a business as an agent: https://allpage.site/docs/guides/set-up-a-business-as-an-agent
- Tools per scope: https://allpage.site/docs/mcp/tools