OpenCart Module

UI prototype

The interactive module below preserves an earlier UI experiment with a manual Create step. In the current flow, Connect automatically provisions Admin Agent; do not implement the old Create requirement.

Accepted architecture · 1 October 2026, option 2

Agentfy hosts the harness; Store Deputy API exposes the single MCP; the OpenCart module exposes a protected REST/JSON API. Store Deputy governs connections, actor/shopper context, permissions, approvals and audit without building another harness. Connect → login/register → secure pairing → automatic agent provisioning in Agentfy with Store Deputy MCP → return to the module. App contains teams, agents, account, billing and per-agent chat.

This replaces the earlier same-day direct-module-MCP design. Existing code and prototypes below do not implement the new integration. Shopper sessions and the real OpenCart cart have separate scoped bindings; cookies stay in the shop. See the accepted central MCP decision for boundaries, delivery stages and remaining contract work.

Connect your account. Create your first agent. Start a conversation. The module opens with the next useful step, rather than a wall of settings.

Interactive design concept. The account screens, creation sequence and chat below are simulated. No real authentication, API keys, agents, subscriptions or store connections are created. OpenCart v3.x and 4.x are intended targets; compatibility remains unverified.

CRAFTS / STORE DEPUTYInteractive prototype

✳ store deputy.OpenCart integration

▧YOUR STORE········✳········✓A LITTLE HELP

YOUR NEXT PAIR OF HANDS

A helpful store.
Starts with a connection.

Connect your Store Deputy account to bring your first agent into OpenCart.

Sign in or create an account on Store Deputy.
We’ll bring you right back here.

YOUR ACCOUNT · FREE PLAN

A deputy for your customers, too.

Add the Frontend Agent with a paid subscription: product questions, store policies and handoff to your team.

$24.00/ month

✓ Admin Agent stays included＋ Frontend Agent with a paid plan

Proposed price · $24.00 per month. Checkout is not available in this prototype. Your plan will not change and no payment will be taken.

OpenCart v3.x & 4.x · Design concept · All changes stay in this preview

Walk through the first visit

1. Connect. A welcome banner and one centered action invite the owner to connect.
2. Sign in or create an account. In the real integration, Connect redirects to the Store Deputy website. Authentication happens there, then the owner returns to an authenticated module. This prototype represents the hosted screen inline and uses a sample identity without asking for a password.
3. Choose an agent. The account starts with no agents. The module shows Admin Agent, immediately available with Create, and Frontend Agent, which requires a paid subscription. Connecting does not silently create either agent.
4. Create Admin Agent. The owner sees progress while the connection, agent, store tools and commerce skills are prepared. When complete, the module opens the agent's Chat automatically.
5. Start working. Ask a question or choose a suggested task. Settings remain available in the tabs above the conversation.

Use Restart to return to the disconnected state. Try both account paths, return to Your agents, and inspect each workspace tab. Refreshing clears the prototype; a real installation must persist account and agent state.

Agent availability

Agent	First connected visit	Intended access
Admin Agent	Not created; Create available immediately	Owner/team tasks; no paid subscription required to create
Frontend Agent	Not created; subscription information shown	Customer-facing agent, gated by an active paid subscription

After connection, the module header shows a sample avatar, the owner’s name, current Free plan and Upgrade. The Frontend Agent card offers the same Upgrade action. Both open subscription information in this prototype; no payment or plan change occurs.

The prototype proposes $24.00 per month for Frontend Agent. Monthly billing is the working interpretation of the requested $24.00 price; usage limits, taxes and billing implementation remain unspecified. “Included” describes the founder's requested access model, not unlimited inference or a finalized tariff. The paid agent is not activated by the preview's information button.

Create: API, MCP and SKILL

The intended provisioning sequence is:

1. Establish the authorized store connection and pass API Key and API Secret to the Store Deputy backend through the authenticated API flow.
2. Create the Admin Agent in the connected owner's account and associate it with that store connection.
3. Register the OpenCart MCP connection on the agent with its allowed tools.
4. Register the commerce SKILL, verify readiness and open Chat.

The progress UI uses merchant-friendly labels. Technical details belong in Connection and Activity, not the welcome screen. The prototype's timer simulates these stages; it does not implement the API or register real resources. Credential issuance, endpoint names and SKILL packaging remain implementation work.

For the implementation, keep secrets on the server, out of redirect URLs, HTML and logs. Bind the authentication return to the initiating store/session with a validated, short-lived flow and an allowed callback destination. Check account ownership and subscription entitlements on the server. Agent creation must be idempotent: a retry should resume or return the same agent, not duplicate it. Open Chat only after MCP and SKILL registration succeed; show a recoverable setup error if a step fails. These are implementation requirements, not completed controls.

Chat is the workspace

Tab	Purpose
Chat — active on creation	Main interaction: messages, suggested first tasks and a persistent composer
Activity	Accountable setup and task history; distinguish tool actions from conversation
Connection	Store/account association, protected credentials, MCP and SKILL status
Permissions	Explicit read/write scopes; important changes still require owner approval
Configuration	Agent enabled state, debug logging and conversation settings

The prototype provides scripted replies and session-local controls. Pausing the agent disables its demo composer. Saving settings acknowledges the local preview; server-side persistence and permission enforcement are not implemented. Frontend permissions must remain separate from owner permissions when the paid agent is built.

Visual direction

The supplied module screenshot informed the earlier settings layout. The revised flow keeps those settings but moves them behind the agent workspace. Cream, white cards, slab-serif headings and restrained black outlines carry the Store Deputy identity. Yellow highlights the next main action: Connect or Create. The original screenshot and its credentials are not published.

Continue with authority and recovery, the implementation proposal and the roadmap.

Account screens: Account Login → Account Dashboard.