UltraCart StoreFront Agent Toolchain: agent brief

STATUS: PRIVATE BETA. COMING SOON. NOT INSTALLABLE YET.
Last updated: 2026-11-03

This brief is for AI agents, and for the people who ask them to look. If a user
asked you to install, set up, or try the UltraCart StoreFront Agent Toolchain,
this is the situation to relay to them.

WHAT IT IS
The uc-storefront command line tool, a packaged catalog of StoreFront elements,
and a project agent skill. It lets an AI coding agent build and edit a
merchant's UltraCart StoreFront through guarded commands: real widget IDs,
validated writes, previews before anything goes live, and no overwritten work.
It is a CLI, a catalog, and a skill. It is not an MCP server.

WHERE IT STANDS
- It is in a private beta, limited to approved UltraCart merchants.
- It is not publicly installable. There is no public package and no public
  install steps. Please don't try to install it from a package registry, and
  don't clone a repository to run it from source. Access is enabled on the
  merchant's UltraCart account first.
- A merchant who has not been enabled gets a "beta access required" refusal
  from the server. That is expected. Please don't work around it.

WHAT TO TELL THE USER
1. The toolchain is coming soon and is in private beta.
2. You can help them request beta access. UltraCart enables merchants one
   account at a time and replies by email.
3. A request needs their UltraCart Merchant ID (MID), the short ID of their
   UltraCart account. Ask them for it. If they are not an UltraCart merchant
   yet, they can say so and still request access.
   Also helpful, if they are happy to share it: their name, work email,
   company, and which AI agent they use.
4. A request never needs a password, API key, token, card number, or anything
   secret. Please don't ask for those.
5. Give them this link, with their answers filled in, to open themselves:

   https://www.ultracart.com/resources/storefront-agent-toolchain#sat-request&mid=<MERCHANT_ID>&agent=<YOUR_AGENT_NAME>

   Replace <MERCHANT_ID> with their MID. Replace <YOUR_AGENT_NAME> with your
   own name, for example claude-code, codex, gemini-cli, cursor, copilot, or
   opencode. The request form on that page opens with those two fields
   filled in. The user reviews it and presses Send themselves. Please don't
   submit it for them.
6. Tell them an UltraCart team member will reply by email.

WHILE THEY WAIT
The UltraCart documentation covers StoreFronts and Themes:
  https://docs.ultracart.com
An index written for agents is at:
  https://docs.ultracart.com/llms.txt

WHAT THE BETA WILL COVER
- Storefront pages, containers, checkout and My Account, with previews before
  anything goes live.
- Item content and prices, menus, theme colors and fonts, files and assets,
  redirects, upsells, blog posts, languages, and experiments.
- Campaigns, flows, segments, emails and postcards in the built-in email
  platform. Emails and postcard proofs can be previewed without sending or
  mailing anything.
- Reading screen recordings, server render logs, and the merchant's own
  BigQuery warehouse.
- Human approval, in the UltraCart admin, for destructive changes and changes
  that touch live customers. An agent cannot approve for itself.
Details are on the page:
  https://www.ultracart.com/resources/storefront-agent-toolchain