# Shopstack agent setup

Set up Shopstack for the user’s purchases and bookings.

Read and follow the canonical Shopstack skill:

https://shopstack.ai/skills/shopstack-checkout/SKILL.md

## Setup sequence

1. Check whether Shopstack MCP is already available. Reuse it; otherwise configure MCP or install the CLI using the canonical skill. Use the installed version’s supported commands.
2. Inspect local profiles before starting signup. Reuse a suitable profile instead of creating a duplicate account.
3. Choose Personal for the user’s own purchases and bookings, including through an agent. Choose Developer for an app or service that manages separate customers. Ask which account type to use only if the task does not make this clear.
4. If a new account is needed, ask for the email address to use and start verified signup. The user opens the time-limited verification email. Continue the pending signup until verification completes; the local tool saves the key privately.
5. For Developer, create a separate end-user profile for each customer. A developer management profile cannot run that customer’s checkout or reservation.
6. Select the intended user profile. Confirm the verified local profile is active. Report the profile name, account type, and available workflows without showing credentials.

## Next task

- Checkout: follow https://shopstack.ai/docs/checkout/mcp/ or https://shopstack.ai/docs/checkout/. Check the active user’s payment connections before selecting Link; Link is optional.
- Reservations: follow https://shopstack.ai/docs/reservations/. Check that the installed client exposes reservation tools first. Reservations are a development preview; do not assume the published client includes them. Reuse current option and time IDs, and obtain explicit confirmation of the exact booking summary before booking.
- Developer accounts and profile switching: https://shopstack.ai/docs/accounts/#developers

For a checkout, show the initiating user the returned private live-view link immediately, then keep reporting meaningful status, activity, and intent changes until Shopstack reaches a typed user boundary or terminal status. Never send the link to another user or a public channel.

MCP cannot enter cards or approve checkout payment. Hand an existing checkout to a trusted SDK/API payment interface. Starting a new CLI checkout does not resume an existing one. Setup alone does not authorize a purchase or booking.

Credentials remain in Shopstack’s private local profile store. Never print or place API keys, signup capabilities, payment-card data, or payment approval in model messages.