Agents
The Agents service manages AI agent instances installed for a store. An agent instance connects a marketplace agent definition to store-specific configuration and operating state.
Dashboard Areas
| Area | Purpose |
|---|---|
| Overview | Review active and total installed agents. |
| Installed Agents | View instance status, description, and configuration access. |
| Marketplace | Find and install additional agent capabilities. |
Install and Operate an Agent
- Open Marketplace from the store.
- Select an agent that supports the intended workflow.
- Review its permissions, dependencies, and configuration requirements.
- Install it for the selected store.
- Configure required MCP, ARP, payment, or extension dependencies.
- Enable the instance after validation.
- Monitor its status and disable it if the workflow is no longer approved.
Usage Scenarios
- Add a catalog assistant for product discovery.
- Install a procurement agent that prepares supplier requests.
- Run a support assistant against approved store tools.
- Pilot a new agent in one store before merchant-wide rollout.
- Disable an instance without removing its marketplace definition from other stores.
Dependency Review
An agent can depend on other store services. Confirm:
- Required MCP servers are installed and healthy.
- ARP endpoints and rules allow only approved traffic.
- Payment providers are configured if the agent can initiate payment workflows.
- Catalog and procurement data are ready.
- Customer-facing channels have an escalation path.
Governance
- Assign an owner to every installed instance.
- Use store-specific configuration instead of shared secrets in prompts.
- Review requested tools and permissions before activation.
- Keep human approval for irreversible or high-value operations.
- Disable unused or unhealthy instances.
- Record production test cases and rollback steps.